Race condition in Linux kernel io_uring/kbuf legacy buffer recycling
CVE-2026-43366 is a Linux kernel flaw in the io_uring/kbuf buffer recycling path. The bug exists in the gap between when a buffer is obtained and when it is later recycled: if the target buffer list becomes empty during that window, another operation can upgrade that list from a legacy provided-buffer list to a ring-provided buffer type before recycle occurs. This race is reachable when a request is forced through io-wq. The vulnerable legacy recycle logic did not verify that the target buffer_list still existed or that it was still the expected legacy type before reusing it. The fix adds validation to ensure the buffer list is still present and still legacy before recycling the buffer.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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
5 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.
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.