Loading vulnerability…
CVE-2023-52672 is a race/order-of-operations flaw in the Linux kernel pipe implementation, introduced by the general notification queue support changes. During pipe ring resizing, the writer wait queue could be awakened before the pipe's maximum usage limit was raised. When a pipe was full before resizing, the awakened writer could still observe the old limit, return to waiting, and receive no subsequent wakeup after the new limit was set. This can leave writes to the resized pipe indefinitely blocked. The correction updates the maximum-usage and accounting state before waking writers, with separate handling for watch queues.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A locally exploitable vulnerability affecting Unity Linux, requiring low privileges and primarily impacting availability according to the supplied CVSS vectors.
Linux kernel pipe synchronization flaw corrected by waking wr_wait after setting max_usage.
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.