Loading vulnerability…
CVE-2025-39698 is an improper failure-cleanup flaw in the Linux kernel io_uring futex wait path. io_futex_wait() allocates io_futex_data and assigns it to an io_kiocb request's async_data field before setting REQ_F_ASYNC_DATA, which identifies the field as valid. On an error path, the futex handler frees the allocation but previously left async_data uncleared. The correction keeps the async-data pointer and validity flag synchronized and clears both on failure cleanup, preventing a stale pointer from remaining associated with the request.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel io_uring/futex flaw where io_futex_wait() does not properly clean up following failure.
A Linux kernel io_uring/futex issue in which io_futex_wait() did not properly clean up after failure.
A Linux kernel io_uring/futex error-path cleanup flaw in io_futex_wait(): allocated io_futex_data could be freed without clearing the request's async_data pointer and associated REQ_F_ASYNC_DATA state. The issue was resolved upstream and in Red Hat Enterprise Linux 9 and 10 advisories.
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.