Skip to content
Fencer Vulns
medium 4.9

CVE-2009-3002 json

The Linux kernel before 2.6.31-rc7 does not initialize certain data structures within getname functions, which allows local users to read t…

published 2009-08-28 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-2987

cvss
4.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
2
Exploit-DB

Summary

The Linux kernel before 2.6.31-rc7 does not initialize certain data structures within getname functions, which allows local users to read the contents of some kernel memory locations by calling getsockname on (1) an AF_APPLETALK socket, related to the atalk_getname function in net/appletalk/ddp.c; (2) an AF_IRDA socket, related to the irda_getname function in net/irda/af_irda.c; (3) an AF_ECONET socket, related to the econet_getname function in net/econet/af_econet.c; (4) an AF_NETROM socket, related to the nr_getname function in net/netrom/af_netrom.c; (5) an AF_ROSE socket, related to the rose_getname function in net/rose/af_rose.c; or (6) a raw CAN socket, related to the raw_getname function in net/can/raw.c.

Patch / fix

  • linux linux_kernel 2.6.31
  • kernel RHEL 3 2.4.21-63.EL
  • kernel-smp RHEL 3 2.4.21-63.EL
  • kernel-BOOT RHEL 3 2.4.21-63.EL
  • kernel-source RHEL 3 2.4.21-63.EL
  • kernel-hugemem RHEL 3 2.4.21-63.EL
  • kernel-unsupported RHEL 3 2.4.21-63.EL
  • kernel-smp-unsupported RHEL 3 2.4.21-63.EL
  • kernel-hugemem-unsupported RHEL 3 2.4.21-63.EL

red hat advisories RHSA-2009:1550RHSA-2009:1540

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-2009-3002 updated cvss 2.1

kernel: numerous getname() infoleaks

  • Red Hat MRG Realtime for RHEL 5 Server kernel-rt 2.6.24.7-137.el5rt, kernel-rt-trace 2.6.24.7-137.el5rt, kernel-rt-vanilla 2.6.24.7-137.el5rt, kernel-rt-debuginfo-common 2.6.24.7-137.el5rt
    fixed: vendor fix RHSA-2009:1540
  • Red Hat Desktop version 3 kernel 2.4.21-63.EL, kernel-smp 2.4.21-63.EL, kernel-BOOT 2.4.21-63.EL, kernel-source 2.4.21-63.EL, kernel-hugemem 2.4.21-63.EL, kernel-unsupported 2.4.21-63.EL, +2 more Red Hat Enterprise Linux AS version 3 kernel 2.4.21-63.EL, kernel-smp 2.4.21-63.EL, kernel-BOOT 2.4.21-63.EL, kernel-source 2.4.21-63.EL, kernel-hugemem 2.4.21-63.EL, kernel-unsupported 2.4.21-63.EL, +2 more Red Hat Enterprise Linux ES version 3 kernel 2.4.21-63.EL, kernel-smp 2.4.21-63.EL, kernel-BOOT 2.4.21-63.EL, kernel-source 2.4.21-63.EL, kernel-hugemem 2.4.21-63.EL, kernel-unsupported 2.4.21-63.EL, +2 more Red Hat Enterprise Linux WS version 3 kernel 2.4.21-63.EL, kernel-smp 2.4.21-63.EL, kernel-BOOT 2.4.21-63.EL, kernel-source 2.4.21-63.EL, kernel-hugemem 2.4.21-63.EL, kernel-unsupported 2.4.21-63.EL, +2 more
    fixed: vendor fix RHSA-2009:1550

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

Timeline

  1. First public exploit (EDB-9521)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-9543 Linux Kernel < 2.6.31-rc7 - 'AF_IRDA' 29-Byte Stack Disclosure (2) local, 2009-08-31
  • EDB-9521 Linux Kernel 2.6.30 - 'atalk_getname()' 8-bytes Stack Disclosure (1) local, 2009-08-26
  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=519305 referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/36150 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
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.