CVE-2026-98417 — net: xfrm: reject unrepresentable espintcp transport headers
In the Linux kernel, the following vulnerability has been resolved: net: xfrm: reject unrepresentable espintcp transport headers ESP-in-TCP can hand xfrm packets whose transport header offset no longer fits after the stream parser trims the TCP envelope. The plain transport header reset truncates that offset and triggers the skb warning path. Use the careful transport-header helper and drop the skb through the existing XFRM error path when the offset cannot be represented.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < d37a5b87577c4b4c1a1dcb000a9dff1df2cf886b≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 6c29681207bc213188afa603dff2d55e7178a341≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 4a8243fd2e21980fa3fd10c0610e9155057cebd3≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < b2b84e73e0386ad0b4f9b8d3afde343e761f5275≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 327b2a457dd7d5445f7395f371f3c65de79bd5ce≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < cce630c751279e974fa0bb574d80575e0cc7e8f3≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 206f396f46149dc8bc4dfd2b54b9879ba3ee1d7d≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and < 96f01b53c2d05e003b040892256de54a586e8529 and 1 moreversion 5.6 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
8 on the record
- git.kernel.org/stable/c/327b2a457dd7d5445f7395f371f3c65de79bd5ce
- git.kernel.org/stable/c/b2b84e73e0386ad0b4f9b8d3afde343e761f5275
- git.kernel.org/stable/c/4a8243fd2e21980fa3fd10c0610e9155057cebd3
- git.kernel.org/stable/c/206f396f46149dc8bc4dfd2b54b9879ba3ee1d7d
- git.kernel.org/stable/c/96f01b53c2d05e003b040892256de54a586e8529
- git.kernel.org/stable/c/cce630c751279e974fa0bb574d80575e0cc7e8f3
- git.kernel.org/stable/c/6c29681207bc213188afa603dff2d55e7178a341
- git.kernel.org/stable/c/d37a5b87577c4b4c1a1dcb000a9dff1df2cf886b
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 7h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 7h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98417 is "net: xfrm: reject unrepresentable espintcp transport headers", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.