In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: reset runtime state when cloning SAs iptfs_clone_state() clones the… (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.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's xfrm subsystem involves the iptfs_clone_state() function, which clones IPTFS mode data using kmemdup(). This cloning copies runtime objects such as sk_buff_head, hrtimers, spinlocks, and in-flight reassembly state that must not be shared between the original and cloned SAs. If the migration of state fails after cloning but before reinitialization, the cloned state can be destroyed with invalid references, causing use-after-free and double-free conditions in iptfs_destroy_state() and skb release paths. The fix involves reinitializing the clone's runtime state before it is published and adjusting module reference handling to prevent premature destruction.
Potential Impact
Exploitation of this vulnerability can lead to use-after-free and double-free conditions in kernel memory management related to IPTFS state cloning. This can cause kernel crashes or potentially allow an attacker to execute arbitrary code or escalate privileges by corrupting kernel memory. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by reinitializing the cloned runtime state before it is published and correcting module reference handling. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed — check the vendor advisory or Linux kernel mailing lists for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: reset runtime state when cloning SAs iptfs_clone_state() clones the… (CVE-2026-63911)
Description
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.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's xfrm subsystem involves the iptfs_clone_state() function, which clones IPTFS mode data using kmemdup(). This cloning copies runtime objects such as sk_buff_head, hrtimers, spinlocks, and in-flight reassembly state that must not be shared between the original and cloned SAs. If the migration of state fails after cloning but before reinitialization, the cloned state can be destroyed with invalid references, causing use-after-free and double-free conditions in iptfs_destroy_state() and skb release paths. The fix involves reinitializing the clone's runtime state before it is published and adjusting module reference handling to prevent premature destruction.
Potential Impact
Exploitation of this vulnerability can lead to use-after-free and double-free conditions in kernel memory management related to IPTFS state cloning. This can cause kernel crashes or potentially allow an attacker to execute arbitrary code or escalate privileges by corrupting kernel memory. However, no known exploits are reported in the wild at this time.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel by reinitializing the cloned runtime state before it is published and correcting module reference handling. Users should apply the official kernel updates that include this fix once available. Patch status is not yet confirmed — check the vendor advisory or Linux kernel mailing lists for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3gc2-w5w2-ffch
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63911"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ab2a4a8d598912fc3f
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 07/19/2026, 20:10:42 UTC
Last updated: 08/31/2026, 10:52:10 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.