CVE-2026-98402: Linux kernel · net: icmp: avoid invalid transport header access in icmp_send tracepoint
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ec6d4612d1c170e1cef1fe55526471da1e81e777 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ec6d4612d1c170e1cef1fe55526471da1e81e777, b972b5e6168dc5d1e13297b1f37f71d6b21cc0f1, 99654b651c6d5fe865798a2adb859767905f9278 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in Linux kernel versions 6.1.189, 6.6.158, and later. Users should upgrade to these or later versions to resolve the issue. No additional mitigation is required as the vulnerability is addressed by the official patch.
Description
A vulnerability in the Linux kernel's ICMP send tracepoint could cause invalid access to the transport header. This occurs because the code unconditionally accesses the UDP header without verifying the packet protocol, potentially triggering warnings or errors under debug configurations. The issue has been fixed by adding proper protocol checks and safer header access methods.
References
- git.kernel.org/stable/c/ec6d4612d1c170e1cef1fe55526471da1e81e777 (opens in a new tab)
- git.kernel.org/stable/c/99654b651c6d5fe865798a2adb859767905f9278 (opens in a new tab)
- git.kernel.org/stable/c/b972b5e6168dc5d1e13297b1f37f71d6b21cc0f1 (opens in a new tab)
- git.kernel.org/stable/c/04c0d35bac5122b533672a6775851dfae84e265e (opens in a new tab)
- git.kernel.org/stable/c/2b32f8c3560905582fb12ed68315a6e606367a6a (opens in a new tab)
- git.kernel.org/stable/c/7fcc2fe39fed1cb98a7374a113ff3800e8f9af80 (opens in a new tab)