Race condition in Linux kernel fs/pipe.c via /proc/*/fd/ anonymous pipe open
CVE-2009-3547 is caused by multiple race conditions in the Linux kernel’s fs/pipe.c (kernels prior to 2.6.32-rc6). A local attacker can trigger the race by attempting to open an anonymous pipe through a /proc/*/fd/ pathname, leading to incorrect concurrent state handling that can result in a NULL pointer dereference and system crash, and in some circumstances can be leveraged for local privilege escalation.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No valid public exploits. Mallory filtered out 5 candidates as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Affected products & vendors
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.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux 2.6.x-era CVE referenced as part of SSHStalker’s legacy exploit module set; specific flaw details are not provided in the content.
A vulnerability chain where a race condition can cause a resource to be released prematurely, leading to a NULL pointer dereference.
The version that knows your environment.
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.