CVE-2026-63911

xfrm: iptfs: reset runtime state when cloning SAs

Published Jul 19, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw lies in the Linux kernel’s IPsec Transformation Services (IPTFS) routine that clones security association state. When iptfs_clone_state() duplicates runtime data with kmemdup(), the clone may retain references to the original packet queue, timers, and locks. If the subsequent migration fails before these fields are reinitialized, the original state can be garbage‑collected, causing the cloned structures to be freed. This triggers use‑after‑free and double‑free errors when packets in the original IPTFS queue are processed, potentially resulting in kernel memory corruption and system crashes. Based on the description, it is inferred that an attacker would need to trigger a migration failure, which typically requires influencing IPsec traffic.

Affected Systems

Linux kernel 7.1 releases (rc1 through rc5) for any architecture are affected. The patch was committed to the mainline kernel; administrators should verify whether their running kernel includes the commit that resets runtime state before publishing the clone.

Risk and Exploitability

With a CVSS score of 7.8, this is a high‑severity vulnerability, but the EPSS score is below 1% and the issue is not in CISA’s KEV catalog, indicating limited current exploitation. An attacker would need to trigger the specific kernel state migration failure, generally requiring local kernel access or the ability to influence IPsec traffic. If successful, the flaw can crash the system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the kernel patch that reinitializes runtime state before publishing the cloned object
  • Upgrade to a kernel release that includes the commit referenced in the advisory
  • If an upgrade is not immediately feasible, disable IPTFS functionality by disabling the corresponding crypto transform or module to prevent the vulnerable code from executing

Generated by OpenCVE AI on October 30, 2026 at 18:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-415
CWE-416
Type Values Removed Values Added
Weaknesses CWE-415
CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
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.
Title xfrm: iptfs: reset runtime state when cloning SAs
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 5, 2026, 12:37 PM
Reserved
Jul 19, 2026, 7:54 AM
Status
Analyzed
Published
Jul 19, 2026, 4:17 PM
Modified
Oct 30, 2026, 2:29 PM
Severity
Public date
Jul 19, 2026, 12:00 AM