CVE-2025-40047 is an improper-synchronization vulnerability in the Linux kernel io_uring waitid implementation. In affected kernels, io_waitid_wait() could return successfully without removing its wait-queue entry when cancellation was in progress. The stale entry could race with a subsequent invocation of the wait-queue callback, causing double callback execution, wait-queue list corruption, and a potential use-after-free condition. The vulnerable code was introduced in Linux kernel 6.7.
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.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel io_uring/waitid vulnerability related to improper pruning of wait queue entries in io_waitid_wait().
A Linux kernel io_uring/waitid vulnerability related to improper wait queue entry pruning in io_waitid_wait().
A Linux kernel vulnerability in io_uring/waitid related to pruning wait queue entries in io_waitid_wait().
A Linux kernel io_uring/waitid vulnerability addressed by ensuring wait-queue entries are pruned in io_waitid_wait().
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.