CVE-2026-63911
In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: reset runtime state when cloning SAs iptfs_clone_state() clones the IPTFS mode data with kmemdup(). This copies runtime objects which must not be shared with the original SA, including the embedded sk_buff_head, hrtimers, spinlock, and in-flight reassembly/reorder state. If xfrm_state_migrate() fails after clone_state() but before the later init_state() call has reinitialized those fields, the cloned state can be destroyed by xfrm_state_gc_task() with list and timer state copied from the original SA. With queued packets this lets the clone splice and free skbs owned by the original IPTFS queue, leading to use-after-free and double-free reports in iptfs_destroy_state() and skb release paths. Reinitialize the clone's runtime state before publishing it through x->mode_data. Because clone_state() now publishes a destroyable mode_data object before init_state(), take the mode callback module reference there. Avoid taking it again from __iptfs_init_state() for the same object.
Affected versions
Linux kernel versions
6.14
and later are affected. Fixed in
6.18.35,
7.0.12,
7.1
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-63911?
CVE-2026-63911 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.14 onward and has been patched in 6.18.35, 7.0.12 and 7.1. CVE-2026-63911 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-63911?
Yes — CVE-2026-63911 has been patched. Fixed versions include 6.18.35, 7.0.12 and 7.1. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-63911 actively exploited?
No — CVE-2026-63911 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.