Kernel warnings via truncated transport-header offsets
Published Oct 14, 2026 · Updated Oct 14, 2026
Transport-offset truncation in Linux Kernel ESP-in-TCP allows attackers to trigger kernel warnings via received ESP-in-TCP packets. In net/xfrm/espintcp.c, handle_esp() resets the transport header without checking whether its offset remains representable after the stream parser removes the TCP envelope. The path requires ESP-in-TCP processing; the published evidence establishes a warning, not a crash or code execution.
Summary
What happened
Transport-offset truncation in Linux Kernel ESP-in-TCP allows attackers to trigger kernel warnings via received ESP-in-TCP packets. In net/xfrm/espintcp.c, handle_esp() resets the transport header without checking whether its offset remains representable after the stream parser removes the TCP envelope. The path requires ESP-in-TCP processing; the published evidence establishes a warning, not a crash or code execution.
The record
- CVE
- CVE-2026-98417
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- Linux Foundation
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.6
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <206f396f46149dc8bc4dfd2b54b9879ba3ee1d7d
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <327b2a457dd7d5445f7395f371f3c65de79bd5ce
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <4a8243fd2e21980fa3fd10c0610e9155057cebd3
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <6c29681207bc213188afa603dff2d55e7178a341
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <96f01b53c2d05e003b040892256de54a586e8529
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <b2b84e73e0386ad0b4f9b8d3afde343e761f5275
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <cce630c751279e974fa0bb574d80575e0cc7e8f3
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <d37a5b87577c4b4c1a1dcb000a9dff1df2cf886b
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started