Skip to content
Fencer Vulns
medium 5.0

CVE-2005-2099 json

The Linux kernel before 2.6.12.5 does not properly destroy a keyring that is not instantiated properly, which allows local users or remote…

published 2005-08-22 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-2100

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

Summary

The Linux kernel before 2.6.12.5 does not properly destroy a keyring that is not instantiated properly, which allows local users or remote attackers to cause a denial of service (kernel oops) via a keyring with a payload that is not empty, which causes the creation to fail, leading to a null dereference in the keyring destructor.

Patch / fix

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

red hat advisories RHSA-2005:514

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-2099 updated

security flaw

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

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

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

CVSS scores

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

Classification

Weakness
  • CWE-399 Resource Management Errors
Technology feeds

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.