Loading vulnerability…
CVE-2026-46274 is a Linux kernel io_uring worker-queue (io-wq) vulnerability in io_wq_remove_pending(). When cancelling pending work, the function updates wq->hash_tail[] if the cancelled item was the tail of its hash bucket. The bug is that it checks whether the predecessor entry in acct->work_list has the same computed hash value, but does not verify that the predecessor is actually a hashed work item. Because io_get_work_hash() derives the hash from flag bits that are unset for non-hashed work, non-hashed work can appear to have hash value 0. As a result, if a hashed bucket-0 work item is cancelled and its list predecessor is a non-hashed work item, the code can incorrectly store a pointer to that non-hashed io_kiocb in wq->hash_tail[0]. That non-hashed work is later dequeued through a fast path that does not clear hash_tail[], so once the io_kiocb completes and is freed, hash_tail[0] becomes a dangling pointer. A subsequent hashed bucket-0 enqueue in io_wq_insert_work() dereferences that stale pointer, and wq_list_add_after() performs a write through freed memory. The fix adds the missing io_wq_is_hashed() check before inheriting a hash_tail[] slot.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.