Linux kernel dmaengine idxd wrong descriptor completion in llist_abort_desc()
CVE-2026-31436 is a vulnerability in the Linux kernel dmaengine idxd component. The flaw is in llist_abort_desc(), where the final list_for_each_entry_safe() loop uses the wrong variable for descriptor completion: at that point d is the traversal cursor for flist, but the code completes found instead. This incorrect completion logic can result in completion of the wrong descriptor or reuse of an invalid pointer state, leading to NULL pointer dereferences, double completion, or descriptor leaks. The upstream fix changes the function to complete d instead of found in the final loop.
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
4 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.