CVE-2009-0676

LOWCVSS v2 · 2.12.1—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 2.1 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:L/Au:N/C:P/I:N/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 0.7% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS v2: 2.1Exploit: Exploit-DB (verified) · public exploitExposed services: Not assessed

A fix is available — apply it.

The sock_getsockopt function in net/core/sock.c in the Linux kernel before 2.6.28.6 does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel memory via an SO_BSDCOMPAT getsockopt request.

CVSS v2.0 (legacy)
2.1LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
2.1LOWlow confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity21% × 45%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 22, 2009

Last Modified

April 23, 2026

References (76)

Vendor Advisories for CVE-2009-0676(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-image-2.6.15-54-hppa64-smp (2.6.15-54.76) @ dapper2026-05-30ubuntu
ubuntulinux-image-2.6.27-11-virtual (2.6.27-11.31) @ intrepid2026-05-30ubuntu
redhatkernel-0:2.6.9-78.0.22.EL2009-04-30redhat
redhatkernel-0:2.6.18-128.1.6.el52009-04-01redhat
redhatkernel-rt-0:2.6.24.7-108.el5rt2009-03-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 2 ecosystems)
Debian:4.0(4)
PackageVulnerable rangeFix by version rangeDependents
fai-kernels1.17 ... 1.17etch1 (27 versions)
  • every version up to 1.17+etch.24etch2: fixed in 1.17+etch.24etch2
—
linux-2.62.6.18.dfsg.1-12 ... 2.6.18.dfsg.1-24etch1 (33 versions)
  • every version up to 2.6.18.dfsg.1-24etch2: fixed in 2.6.18.dfsg.1-24etch2
—
linux-2.6.242.6.24-5~etchnhalf.1 ... 2.6.24-6~etchnhalf.8 (9 versions)
  • every version up to 2.6.24-6~etchnhalf.8etch1: fixed in 2.6.24-6~etchnhalf.8etch1
—
user-mode-linux2.6.18-1um-2 ... 2.6.18-1um-2etch4 (25 versions)
  • every version up to 2.6.18-1um-2etch.24etch2: fixed in 2.6.18-1um-2etch.24etch2
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
linux-2.62.6.26-13, 2.6.26-13lenny2~bpo40+1
  • every version up to 2.6.26-13lenny2: fixed in 2.6.26-13lenny2
—

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 128 total refreshes for this CVE.

  1. 2026-10-09 20:00 UTCEPSS rescore
  2. 2026-10-08 16:33 UTCEPSS rescore
  3. 2026-10-07 23:37 UTCEPSS rescore
  4. 2026-10-06 15:09 UTCEPSS rescore
  5. 2026-10-05 17:37 UTCEPSS rescore
  6. 2026-10-04 23:15 UTCEPSS rescore
  7. 2026-09-30 14:58 UTCEPSS rescore
  8. 2026-09-29 07:57 UTCEG score recompute
  9. 2026-09-27 13:39 UTCEPSS rescore
  10. 2026-09-26 15:52 UTCEPSS rescore
  11. 2026-09-24 13:57 UTCEPSS rescore
  12. 2026-09-17 19:20 UTCEPSS rescore
  13. 2026-09-15 03:04 UTCEPSS rescore
  14. 2026-09-13 16:40 UTCEPSS rescore
  15. 2026-09-12 14:54 UTCEPSS rescore
  16. 2026-09-10 09:24 UTCEPSS rescore
  17. 2026-09-06 13:41 UTCEPSS rescore
  18. 2026-09-05 15:22 UTCEPSS rescore
  19. 2026-09-04 13:55 UTCEPSS rescore
  20. 2026-08-28 21:34 UTCEPSS rescore
  21. 2026-08-27 14:19 UTCEPSS rescore
  22. 2026-08-25 13:43 UTCEPSS rescore
  23. 2026-08-19 16:58 UTCEPSS rescore
  24. 2026-08-15 01:24 UTCEPSS rescore
  25. 2026-08-09 13:41 UTCEPSS rescore
Show 75 more
  1. 2026-08-08 16:31 UTCEPSS rescore
  2. 2026-08-06 13:41 UTCEPSS rescore
  3. 2026-08-03 10:28 UTCEPSS rescore
  4. 2026-07-30 16:22 UTCEPSS rescore
  5. 2026-07-30 01:26 UTCEPSS rescore
  6. 2026-07-26 13:37 UTCEG score recompute▲ 2.10
  7. 2026-07-25 14:12 UTCEPSS rescore
  8. 2026-07-24 14:12 UTCEPSS rescore
  9. 2026-07-23 14:14 UTCEPSS rescore
  10. 2026-07-23 00:58 UTCEG score recompute
  11. 2026-07-23 00:36 UTCEG score recompute
  12. 2026-07-23 00:03 UTCEG score recompute
  13. 2026-07-22 21:42 UTCEG score recompute
  14. 2026-07-22 14:03 UTCEPSS rescore
  15. 2026-07-21 15:20 UTCEPSS rescore
  16. 2026-07-20 17:03 UTCEPSS rescore
  17. 2026-07-20 17:03 UTCEPSS rescore
  18. 2026-07-18 09:59 UTCEPSS rescore
  19. 2026-07-16 16:58 UTCEPSS rescore
  20. 2026-07-15 16:54 UTCEPSS rescore
  21. 2026-07-15 16:54 UTCEPSS rescore
  22. 2026-07-15 01:55 UTCEPSS rescore
  23. 2026-07-13 22:25 UTCEPSS rescore
  24. 2026-07-13 06:07 UTCEPSS rescore
  25. 2026-07-11 08:22 UTCEPSS rescore
  26. 2026-07-11 08:22 UTCEPSS rescore
  27. 2026-07-09 19:04 UTCEPSS rescore
  28. 2026-07-08 15:10 UTCEPSS rescore
  29. 2026-07-06 16:23 UTCEPSS rescore
  30. 2026-07-06 02:19 UTCEPSS rescore
  31. 2026-07-06 02:19 UTCEPSS rescore
  32. 2026-07-05 02:26 UTCEPSS rescore
  33. 2026-07-05 02:26 UTCEPSS rescore
  34. 2026-07-04 06:27 UTCEPSS rescore
  35. 2026-07-01 15:02 UTCEPSS rescore
  36. 2026-06-30 23:19 UTCEPSS rescore
  37. 2026-06-28 14:03 UTCEPSS rescore
  38. 2026-06-28 04:52 UTCEPSS rescore
  39. 2026-06-28 04:52 UTCEPSS rescore
  40. 2026-06-27 03:05 UTCEPSS rescore
  41. 2026-06-25 13:46 UTCEPSS rescore
  42. 2026-06-25 13:46 UTCEPSS rescore
  43. 2026-06-24 14:02 UTCEPSS rescore
  44. 2026-06-24 14:02 UTCEPSS rescore
  45. 2026-06-23 21:29 UTCEPSS rescore
  46. 2026-06-23 21:29 UTCEPSS rescore
  47. 2026-06-22 14:22 UTCEPSS rescore
  48. 2026-06-22 14:22 UTCEPSS rescore
  49. 2026-06-21 14:53 UTCEPSS rescore
  50. 2026-06-21 01:56 UTCEPSS rescore
  51. 2026-06-21 01:56 UTCEPSS rescore
  52. 2026-06-19 19:22 UTCEPSS rescore
  53. 2026-06-19 19:22 UTCEPSS rescore
  54. 2026-06-18 17:49 UTCEPSS rescore
  55. 2026-06-18 17:49 UTCEPSS rescore
  56. 2026-06-17 17:49 UTCEPSS rescore
  57. 2026-06-17 17:49 UTCEPSS rescore
  58. 2026-06-16 17:49 UTCEPSS rescore
  59. 2026-06-16 17:49 UTCEPSS rescore
  60. 2026-06-15 17:44 UTCEPSS rescore
  61. 2026-06-14 23:14 UTCEPSS rescore
  62. 2026-06-14 23:14 UTCEPSS rescore
  63. 2026-06-13 22:57 UTCEPSS rescore
  64. 2026-06-12 23:08 UTCEPSS rescore
  65. 2026-06-12 23:08 UTCEPSS rescore
  66. 2026-06-10 22:14 UTCEPSS rescore
  67. 2026-06-10 13:17 UTCEPSS rescore
  68. 2026-06-08 14:13 UTCEPSS rescore
  69. 2026-06-07 15:22 UTCEPSS rescore
  70. 2026-06-07 15:22 UTCEPSS rescore
  71. 2026-06-06 13:44 UTCEPSS rescore
  72. 2026-06-06 13:44 UTCEPSS rescore
  73. 2026-06-06 13:44 UTCEPSS rescore
  74. 2026-06-05 22:44 UTCEPSS rescore
  75. 2026-06-05 22:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-32805✓ verified
    First seen Feb 20, 2009

    Linux Kernel 2.6.x - 'sock.c' SO_BSDCOMPAT Option Information Disclosure

    Open source ↗

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2009-0676?
CVE-2009-0676 is a low vulnerability published on February 22, 2009. The sockgetsockopt function in net/core/sock.c in the Linux kernel before 2.6.28.6 does not initialize a certain structure member, which allows local users to obtain potentially sensitive information from kernel memory via an SOBSDCOMPAT getsockopt request.
When was CVE-2009-0676 disclosed?
CVE-2009-0676 was first published on February 22, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-0676 actively exploited?
CVE-2009-0676 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-0676?
A fix for CVE-2009-0676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2009-0676 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2009-0676

Explore →

Is Your Infrastructure Affected by CVE-2009-0676?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs