Skip to content
Fencer Vulns
low 1.2

CVE-2005-0937 json

Some futex functions in futex.c for Linux kernel 2.6.x perform get_user calls while holding the mmap_sem semaphore, which could allow local…

published 2005-02-22 21 y ago modified 2026-06-16 4 mo ago also EUVD-2005-0938

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

Summary

Some futex functions in futex.c for Linux kernel 2.6.x perform get_user calls while holding the mmap_sem semaphore, which could allow local users to cause a deadlock condition in do_page_fault by triggering get_user faults while another thread is executing mmap or other functions.

Patch / fix

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

red hat advisories RHSA-2005:420

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

security flaw

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

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.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 1.2 AV:L/AC:H/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.