CVE-2026-98850: Linux kernel · net/packet: prevent TX_RING byte count overflow
Source GCVE Database
Not known to be exploited · fixed in be12b221c0301111eeb023be04add3c6ad7c21fe : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in be12b221c0301111eeb023be04add3c6ad7c21fe, ae169d318d5d23bac76ece90a7e2b5cb760ed043, 69ca64bbb528898916f309552053c32a04a36ebc +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 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
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented to prevent the TX_RING byte count from overflowing by stopping before the count would exceed INT_MAX. Users should apply the official Linux kernel patch that addresses this issue. Since this is a kernel-level vulnerability, updating to a patched kernel version is the recommended remediation. No other mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's net/packet subsystem involving TX_RING byte count overflow has been resolved. The issue arises because tpacket_snd() accumulates packet lengths in a signed integer, which can overflow into the negative range after many transmissions. This causes sock_sendmsg_nosec() to misinterpret the value and trigger a kernel BUG, potentially leading to a kernel panic on systems configured to panic on oops. The flaw allows a CAP_NET_RAW user to cause a host kernel panic. The fix prevents the byte count from exceeding INT_MAX by stopping before the overflow occurs.
References
- nvd.nist.gov/vuln/detail/CVE-2026-98850 (opens in a new tab)
- git.kernel.org/stable/c/2cf81fc9505b148b1b70068303ea6ea4b1212403 (opens in a new tab)
- git.kernel.org/stable/c/69ca64bbb528898916f309552053c32a04a36ebc (opens in a new tab)
- git.kernel.org/stable/c/9fd63d284e251332f4874ef9023cde472f315f86 (opens in a new tab)
- git.kernel.org/stable/c/be12b221c0301111eeb023be04add3c6ad7c21fe (opens in a new tab)
- git.kernel.org/stable/c/ae169d318d5d23bac76ece90a7e2b5cb760ed043 (opens in a new tab)