CVE-2026-98503: Linux kernel · packet: use ubuf_info completion for TX_RING packets
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eda9bcb721f15a93746a99eabda33d80b86404fd : patch Linux kernel soon.
Data as of 26 Oct 2026, 13:47 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in eda9bcb721f15a93746a99eabda33d80b86404fd, e67c455d79fbf709a94965f09a2be6bf4f4ba5fd, 9518405613863d0bf0700927a21367f5942cf058 +3
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/kernelpkg:rpm/linux/kernelOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability has been fixed in Linux kernel versions 4.15, 4.20, and specific commits identified by their hashes. Users should upgrade to these fixed versions or later to mitigate the issue. No additional action is required beyond applying the official patches.
Description
CVE-2026-98503 is a vulnerability in the Linux kernel's packet subsystem involving the handling of TX_RING packets. The issue arises from premature release of ring slots due to skb destructor calls, which could lead to reuse of slots still linked to socket buffers. The fix involves switching to standard zerocopy completion to ensure slots are only released after all references are freed or copied, preventing in-flight state aliasing and improving memory management.
References
- git.kernel.org/stable/c/e67c455d79fbf709a94965f09a2be6bf4f4ba5fd (opens in a new tab)
- git.kernel.org/stable/c/eda9bcb721f15a93746a99eabda33d80b86404fd (opens in a new tab)
- git.kernel.org/stable/c/2a0c9afefc0ecea2cc30ccfbbbc98182a0986191 (opens in a new tab)
- git.kernel.org/stable/c/9518405613863d0bf0700927a21367f5942cf058 (opens in a new tab)