Description
In the Linux kernel, the following vulnerability has been resolved:

xfrm: iptfs: fix runt reassembly panic from short inner tot_len

When the start of an inner packet is split across two outer packets
such that fewer than 4 bytes land at the end of the first one,
__input_process_payload() saves those bytes as a runt and skips the
iplen/iphlen validation performed for in-place packets. When the
continuation packet arrives, iptfs_reassem_cont() only requires the
declared inner length to be >= sizeof(ra_runt) (6) before allocating
the reassembly skb with that attacker-controlled length.

However, __iptfs_iphlen() always returns the fixed minimum IP header
size (20 for IPv4, 40 for IPv6), so for an inner IPv4 tot_len in
[6, 19] the header-completion copy writes past the declared packet
length, and the subsequent "ipremain -= copylen" underflows to ~4GB,
leaving the payload copy length bounded only by blkoff (up to 64KB).
At runtime the skb_put() tailroom check turns this into
skb_over_panic(), i.e. an unprivileged kernel panic (DoS), reachable
locally via userns+netns IPTFS SAs and remotely against IPTFS VPN
gateways when the decrypted outer skb is linear (e.g. AF_PACKET taps,
tun/tap delivery).

Align the runt path with the normal path by requiring the declared
inner length to cover at least the IP header size. This also subsumes
the previous >= sizeof(ra_runt) check, since the minimum IP header
is always larger than the runt buffer.

This issue was found by the autokbug dynamic kernel fuzzer at
Tencent Yunding Lab.
Published: 2026-10-06
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Kernel Denial of Service
Action: Apply Patch
AI Analysis

Impact

The Linux kernel’s IPTFS reassembly code mismanages an inner packet fragment that crosses an outer packet boundary, creating a runt fragment that bypasses normal IP length validation. An attacker sending a crafted inner packet with a total length between 6 and 19 bytes causes the kernel to write beyond the intended buffer while completing the inner header, leading to a kernel panic. This flaw is an instance of improper bounds checking that corrupts kernel memory. The resulting crash halts the host, delivering a denial‑of‑service condition.

Affected Systems

All Linux kernel installations that enable IPTFS or operate an IPTFS VPN gateway are potentially impacted. The issue affects any kernel version prior to the commit that aligns the runt path with the normal reassembly logic. Systems that do not use the IPTFS subsystem or have that feature disabled are not affected.

Risk and Exploitability

The EPSS score is less than 1 % and the vulnerability is not listed in the CISA KEV catalog, yet an unprivileged attacker can trigger it by sending or receiving specially crafted IPTFS traffic. The CVSS score of 5.5 indicates moderate severity. The flaw can be reached locally via user‑namespace IPTFS security associations or remotely through an IPTFS VPN gateway, making the threat viable against hosts that process such traffic. No additional system or software prerequisites beyond the presence of IPTFS are required, so the attack vector is straightforward for any entity capable of injecting or observing the relevant packets.

Generated by OpenCVE AI on October 9, 2026 at 03:39 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the IPTFS reassembly patch referenced in the advisory commits.
  • Disable IPTFS on systems where it is not required, or block inbound IPTFS traffic to prevent the exploit from reaching vulnerable hosts.
  • Configure network interfaces to avoid linear outer SKBs for IPTFS traffic, ensuring packet processing does not use unverified linear data.

Generated by OpenCVE AI on October 9, 2026 at 03:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 09 Oct 2026 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate


Wed, 07 Oct 2026 04:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787

Tue, 06 Oct 2026 19:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-122

Tue, 06 Oct 2026 14:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-122

Tue, 06 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: fix runt reassembly panic from short inner tot_len When the start of an inner packet is split across two outer packets such that fewer than 4 bytes land at the end of the first one, __input_process_payload() saves those bytes as a runt and skips the iplen/iphlen validation performed for in-place packets. When the continuation packet arrives, iptfs_reassem_cont() only requires the declared inner length to be >= sizeof(ra_runt) (6) before allocating the reassembly skb with that attacker-controlled length. However, __iptfs_iphlen() always returns the fixed minimum IP header size (20 for IPv4, 40 for IPv6), so for an inner IPv4 tot_len in [6, 19] the header-completion copy writes past the declared packet length, and the subsequent "ipremain -= copylen" underflows to ~4GB, leaving the payload copy length bounded only by blkoff (up to 64KB). At runtime the skb_put() tailroom check turns this into skb_over_panic(), i.e. an unprivileged kernel panic (DoS), reachable locally via userns+netns IPTFS SAs and remotely against IPTFS VPN gateways when the decrypted outer skb is linear (e.g. AF_PACKET taps, tun/tap delivery). Align the runt path with the normal path by requiring the declared inner length to cover at least the IP header size. This also subsumes the previous >= sizeof(ra_runt) check, since the minimum IP header is always larger than the runt buffer. This issue was found by the autokbug dynamic kernel fuzzer at Tencent Yunding Lab.
Title xfrm: iptfs: fix runt reassembly panic from short inner tot_len
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:18:23.197Z

Reserved: 2026-09-25T10:25:14.344Z

Link: CVE-2026-98371

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-06T09:18:31.613

Modified: 2026-10-19T10:18:40.323

Link: CVE-2026-98371

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-06T00:00:00Z

Links: CVE-2026-98371 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-09T03:45:16Z

Weaknesses