Skip to content
Fencer Vulns
medium 5.0

CVE-2005-2098 json

The KEYCTL_JOIN_SESSION_KEYRING operation in the Linux kernel before 2.6.12.5 contains an error path that does not properly release the ses…

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

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

Summary

The KEYCTL_JOIN_SESSION_KEYRING operation in the Linux kernel before 2.6.12.5 contains an error path that does not properly release the session management semaphore, which allows local users or remote attackers to cause a denial of service (semaphore hang) via a new session keyring (1) with an empty name string, (2) with a long name string, (3) with the key quota reached, or (4) ENOMEM.

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-2098 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.20% 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

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.