Loading vulnerability…
CVE-2026-63911 is a memory-safety vulnerability in the Linux kernel's xfrm IP-TFS mode handling during Security Association (SA) cloning. The flaw arises because iptfs_clone_state() duplicates IPTFS mode data with kmemdup(), performing a shallow copy of runtime-only objects that must remain unique to each SA instance. Copied state includes queueing and synchronization primitives such as the embedded sk_buff_head, hrtimers, spinlock, and in-flight reassembly and reorder state. If xfrm_state_migrate() fails after clone_state() but before init_state() reinitializes the cloned runtime fields, the cloned SA may later be destroyed by xfrm_state_gc_task() while still containing runtime state copied from the original SA. In that condition, destruction of the clone can manipulate and free socket buffers owned by the original IPTFS queue, resulting in use-after-free and double-free conditions in iptfs_destroy_state() and skb release paths.
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.
1 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.