CVE-2009-1961 is a deadlock vulnerability in the Linux kernel OCFS2 filesystem inode double-locking implementation. A sequence of splice system calls can create a circular lock dependency among generic_file_splice_write, splice_from_pipe, and ocfs2_file_splice_write. The resulting deadlock blocks OCFS2 file-creation and file-removal operations. Affected versions include Linux kernel 2.6.30 before 2.6.30-rc3, 2.6.29 before 2.6.29.4, and 2.6.27 before 2.6.27.24; versions back to 2.6.19 may also be affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A local denial-of-service vulnerability in the Linux kernel OCFS2 filesystem's inode locking and splice-write handling. Crafted splice system calls can deadlock filesystem operations, preventing file creation and removal.
An operating system deadlock vulnerability involving three separate functions.
An operating-system deadlock involving three separate functions.
An operating-system deadlock involving three separate functions.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.