Loading vulnerability…
CVE-2026-31663 is a Linux kernel xfrm vulnerability caused by releasing a network device reference too early in the xfrm input path after asynchronous cryptographic processing completes. On async re-entry, xfrm_input_resume() called dev_put() before the skb reached transport_finish. The skb->dev pointer was subsequently used by NF_HOOK and its okfn, creating a race with concurrent network device teardown. The upstream fix removes the early dev_put() from the async resumption path and instead drops the device reference only after the NF_HOOK call in transport_finish, using a saved device pointer because NF_HOOK may consume the skb. The fix also ensures references are released correctly for non-transport exits such as decapsulation, GRO, and drop paths, as well as secondary async return points.
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.
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.
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.