Quick answers
- Is CVE-2026-98371 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98371 being exploited in the wild.
- How severe is CVE-2026-98371?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Linux Kernel unspecified.
- Is there a fix for CVE-2026-98371?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-98371 attacked?
- It is attacked over the network or with local access, in an operating system.
- Am I affected by CVE-2026-98371?
- Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the runt packet reassembly path of the IPTFS implementation, where insufficient validation of the declared inner packet length allows a buffer overflow and integer underflow in __iptfs_iphlen() processing. When an IPv4 packet header is split across outer packets with a declared length between 6 and 19 bytes, the reassembly logic incorrectly calculates payload copy lengths, leading to skb_over_panic() in the kernel. The fix requires validating that the declared inner length covers at least the minimum IP header size before allocating reassembly buffers.
Affected products
- Linux kernel unspecified
Timeline
- 2026-10-06: disclosed