CVE-2009-3547

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2022-05-02. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 5%CVSS: 7.0Exploit: NoneExposed: 0

A fix is available — apply it.

Multiple race conditions in fs/pipe.c in the Linux kernel before 2.6.32-rc6 allow local users to cause a denial of service (NULL pointer dereference and system crash) or gain privileges by attempting to open an anonymous pipe via a /proc/*/fd/ pathname.

CVSS v3
7.0
EG Score
7.0(medium)
EPSS
91.2%
KEV
Not listed

Published

November 4, 2009

Last Modified

April 23, 2026

References (58)

Vendor Advisories for CVE-2009-3547(7)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-2.6.31-16-powerpc (2.6.31-16.52) @ karmic2026-05-30ubuntu
redhatkernel-0:2.6.18-92.1.32.el52009-12-15redhat
redhatkernel-0:2.6.18-128.11.1.el52009-11-17redhat
redhatkernel-0:2.6.9-78.0.28.EL2009-11-17redhat
redhatkernel-rt-0:2.6.24.7-137.el5rt2009-11-03redhat
redhatkernel-0:2.4.21-63.EL2009-11-03redhat
redhatkernel-0:2.6.9-89.0.16.EL2009-11-03redhat
redhatkernel-0:2.6.18-164.6.1.el52009-11-03redhat

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

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 / 33× 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.

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

Publicly available exploits

(5 references)

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

  • Exploit-DBEDB-40812
    First seen Dec 16, 2013

    Linux Kernel 2.6.10 < 2.6.31.5 - 'pipe.c' Local Privilege Escalation

    Open source ↗
  • Exploit-DBEDB-10018✓ verified
    First seen Nov 12, 2009

    Linux Kernel 2.6.32 - 'pipe.c' Local Privilege Escalation (4)

    Open source ↗
  • Exploit-DBEDB-9844✓ verified
    First seen Nov 5, 2009

    Linux Kernel 2.4.1 < 2.4.37 / 2.6.1 < 2.6.32-rc5 - 'pipe.c' Local Privilege Escalation (3)

    Open source ↗
  • Exploit-DBEDB-33321✓ verified
    First seen Nov 3, 2009

    Linux Kernel 2.6.0 < 2.6.31 - 'pipe.c' Local Privilege Escalation (1)

    Open source ↗
  • Exploit-DBEDB-33322✓ verified
    First seen Nov 3, 2009

    Linux Kernel 2.6.x - 'pipe.c' Local Privilege Escalation (2)

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2009-3547?
CVE-2009-3547 is a high vulnerability published on November 4, 2009. Multiple race conditions in fs/pipe.c in the Linux kernel before 2.6.32-rc6 allow local users to cause a denial of service (NULL pointer dereference and system crash) or gain privileges by attempting to open an anonymous pipe via a /proc/*/fd/ pathname.
When was CVE-2009-3547 disclosed?
CVE-2009-3547 was first published in the National Vulnerability Database on November 4, 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-3547 actively exploited?
CVE-2009-3547 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2009-3547?
CVE-2009-3547 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2009-3547?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-3547, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-3547

Explore →

Is Your Infrastructure Affected by CVE-2009-3547?

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

Start Free Scan →Browse All CVEs