Skip to content
Fencer Vulns
low 2.1

CVE-2005-0092 json

Unknown vulnerability in the Red Hat Enterprise Linux 4 kernel 4GB/4GB split patch, when running on x86 with the hugemem kernel, allows loc…

published 2005-02-19 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0093

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

Unknown vulnerability in the Red Hat Enterprise Linux 4 kernel 4GB/4GB split patch, when running on x86 with the hugemem kernel, allows local users to cause a denial of service (crash).

Patch / fix

  • kernel RHEL 4 2.6.9-5.0.3.EL
  • kernel-smp RHEL 4 2.6.9-5.0.3.EL
  • kernel-hugemem RHEL 4 2.6.9-5.0.3.EL

red hat advisories RHSA-2005:092

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2005-0092 updated

security flaw

  • Red Hat Enterprise Linux AS version 4 kernel 2.6.9-5.0.3.EL, kernel-smp 2.6.9-5.0.3.EL, kernel-hugemem 2.6.9-5.0.3.EL Red Hat Enterprise Linux Desktop version 4 kernel 2.6.9-5.0.3.EL, kernel-smp 2.6.9-5.0.3.EL, kernel-hugemem 2.6.9-5.0.3.EL Red Hat Enterprise Linux ES version 4 kernel 2.6.9-5.0.3.EL, kernel-smp 2.6.9-5.0.3.EL, kernel-hugemem 2.6.9-5.0.3.EL Red Hat Enterprise Linux WS version 4 kernel 2.6.9-5.0.3.EL, kernel-smp 2.6.9-5.0.3.EL, kernel-hugemem 2.6.9-5.0.3.EL
    fixed: vendor fix RHSA-2005:092

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.