CVE-2009-1961

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
4.7
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 4.7Exploit: NoneExposed: 0

A fix is available — apply it.

The inode double locking code in fs/ocfs2/file.c in the Linux kernel 2.6.30 before 2.6.30-rc3, 2.6.27 before 2.6.27.24, 2.6.29 before 2.6.29.4, and possibly other versions down to 2.6.19 allows local users to cause a denial of service (prevention of file creation and removal) via a series of splice system calls that trigger a deadlock between the generic_file_splice_write, splice_from_pipe, and ocfs2_file_splice_write functions.

CVSS v3
4.7
EG Score
4.7(medium)
EPSS
44.6%
KEV
Not listed

Published

June 8, 2009

Last Modified

April 23, 2026

References (40)

Vendor Advisories for CVE-2009-1961(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-image-2.6.28-13-server (2.6.28-13.45) @ jaunty2026-05-30ubuntu
redhatkernel-rt-0:2.6.24.7-126.el5rt2009-07-14redhat

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(2)

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

    Linux Kernel 2.6.x - 'splice(2)' Double Lock Local Denial of Service

    Open source ↗

Frequently asked(5)

What is CVE-2009-1961?
CVE-2009-1961 is a medium vulnerability published on June 8, 2009. The inode double locking code in fs/ocfs2/file.c in the Linux kernel 2.6.30 before 2.6.30-rc3, 2.6.27 before 2.6.27.24, 2.6.29 before 2.6.29.4, and possibly other versions down to 2.6.19 allows local users to cause a denial of service (prevention of file creation and removal) via a series of splice…
When was CVE-2009-1961 disclosed?
CVE-2009-1961 was first published in the National Vulnerability Database on June 8, 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-1961 actively exploited?
CVE-2009-1961 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2009-1961?
CVE-2009-1961 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2009-1961?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2009-1961, 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-1961

Explore →

Is Your Infrastructure Affected by CVE-2009-1961?

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

Start Free Scan →Browse All CVEs