CVE-2026-98372
Received Received - Intake

BaseFortify

Vulnerability report for CVE-2026-98372, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-06

Last updated on: 2026-10-06

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: fix stack OOB read in iptfs_skb_reset_frag_walk() iptfs_skb_reset_frag_walk() advances to the fragment containing @offset with an unbounded loop: while (offset >= walk->past + walk->frags[walk->fragi].len) walk->past += walk->frags[walk->fragi++].len; walk->fragi is advanced and walk->frags[walk->fragi] is dereferenced without ever checking fragi against walk->nr_frags. When the requested offset is at or beyond the total length spanned by the walk's fragments, fragi runs past nr_frags and off the end of the fixed-size on-stack frags[MAX_SKB_FRAGS + 1] array, reading out-of-bounds stack memory. The two callers behave differently: iptfs_skb_add_frags() already guards against this with if (!walk->nr_frags || offset >= walk->total + walk->initial_offset) return len; but iptfs_skb_can_add_frags() has no such guard and calls iptfs_skb_reset_frag_walk() unconditionally, so it performs the out-of-range walk. Its own "fragi < walk->nr_frags" bound check runs only afterwards, too late to prevent the read. This is reachable from the receive path: a crafted IP-TFS (AGGFRAG) payload delivered to an IPTFS SA drives iptfs_reassem_cont() -> iptfs_skb_can_add_frags() with an offset past the fragment total, e.g.: BUG: KASAN: stack-out-of-bounds in iptfs_skb_reset_frag_walk+0x235/0x250 Read of size 4 at addr ffff888008ad7210 by task repro/345 iptfs_skb_reset_frag_walk+0x235/0x250 net/xfrm/xfrm_iptfs.c:392 iptfs_skb_can_add_frags+0x155/0x310 net/xfrm/xfrm_iptfs.c:420 iptfs_reassem_cont+0xcf8/0x1140 net/xfrm/xfrm_iptfs.c:902 iptfs_input_ordered+0x552/0x670 net/xfrm/xfrm_iptfs.c:1280 iptfs_input+0x3d6/0xde0 net/xfrm/xfrm_iptfs.c:1741 xfrm_input+0x282f/0x6140 net/xfrm/xfrm_input.c:700 xfrm4_esp_rcv+0x93/0x120 net/ipv4/xfrm4_protocol.c:104 ip_rcv+0x278/0x2d0 net/ipv4/ip_input.c:612 Give iptfs_skb_can_add_frags() the same up-front guard that iptfs_skb_add_frags() already has, so the walk is never entered with an out-of-range offset. When it triggers, the caller falls back to the existing linearize-and-copy path, which is safe.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-06
Last Modified
2026-10-06
Generated
2026-10-19
AI Q&A
2026-10-06
EPSS Evaluated
2026-10-18
NVD
EUVD

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
Linux Linux 5f2b6a9095743a6bf1f34c43c4fe78fa8bdf5ad7
Linux Linux 5f2b6a9095743a6bf1f34c43c4fe78fa8bdf5ad7
Linux Linux 5f2b6a9095743a6bf1f34c43c4fe78fa8bdf5ad7
Linux Linux 6.14

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a stack out-of-bounds (OOB) read vulnerability in the Linux kernel's xfrm iptfs component. It occurs in the function iptfs_skb_reset_frag_walk() when processing crafted IP-TFS payloads. The function advances through packet fragments without properly checking array bounds, leading to memory corruption.

Detection Guidance

This vulnerability is specific to the Linux kernel's xfrm subsystem and IPTFS (IP Traffic Flow Security) implementation. Detection requires kernel-level inspection. Check if your system uses IPTFS by examining kernel logs for xfrm_iptfs errors or stack out-of-bounds reports. Monitor for crashes in xfrm_input or related network paths.

Impact Analysis

An attacker could exploit this to read sensitive kernel memory, potentially exposing confidential data or causing system instability. It may lead to crashes or privilege escalation if combined with other exploits.

Compliance Impact

This vulnerability is a stack out-of-bounds read in the Linux kernel's IP-TFS (IP Traffic Flow Security) implementation. It does not directly impact data confidentiality, integrity, or availability in a way that would violate GDPR or HIPAA requirements. The issue is limited to a memory read error during packet processing and does not involve unauthorized data access or modification.

Mitigation Strategies

Apply the kernel patch that fixes this issue. If you cannot patch immediately, disable IPTFS functionality by setting module parameters or recompiling the kernel without IPTFS support. Monitor vendor advisories for updates and restrict untrusted network access to systems using IPTFS.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98372. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart