CVE-2026-98300: Linux kernel · tcp: Don't call skb_clone_and_charge_r() for close()d listener in tcp_v6_do_rcv().
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b727e3d58cb906f1506c1334dfba71fbb1338339 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b727e3d58cb906f1506c1334dfba71fbb1338339, a23a3bc5004df6434de05797e0b6b2ecf864b86a, 619bfbaacbff6a9822923f69f6af29d7f66a870c +5
Exploitation evidence
Disclosed: evidence found.
CVE published 6 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 is available in multiple Linux kernel commits as listed in the established facts. Users should update to a Linux kernel version that includes these fixes to resolve the race condition. No additional mitigation is required beyond applying the official patch.
Description
A race condition in the Linux kernel's TCP IPv6 receive path could cause a function to be called locklessly on a closed socket, leading to a kernel warning and potential instability. The issue arises when tcp_v6_do_rcv() calls skb_clone_and_charge_r() for a listener socket that has been concurrently closed, changing its state from TCP_LISTEN to TCP_CLOSE. This vulnerability has been addressed by avoiding the call to skb_clone_and_charge_r() for sockets in TCP_CLOSE state as well.
References
- git.kernel.org/stable/c/a23a3bc5004df6434de05797e0b6b2ecf864b86a (opens in a new tab)
- git.kernel.org/stable/c/1cb7f292a337fdc72a8219bcd9d40a9cf5e86db5 (opens in a new tab)
- git.kernel.org/stable/c/7d94602e77a4525611afebb23149145ac242afd7 (opens in a new tab)
- git.kernel.org/stable/c/b727e3d58cb906f1506c1334dfba71fbb1338339 (opens in a new tab)
- git.kernel.org/stable/c/3e3394a13b603cc79b6a35480b8e20df6c716944 (opens in a new tab)
- git.kernel.org/stable/c/619bfbaacbff6a9822923f69f6af29d7f66a870c (opens in a new tab)
- git.kernel.org/stable/c/56d38839ef0bff6526d9bd73b6811bd00316b21c (opens in a new tab)
- git.kernel.org/stable/c/8e759cd1f6444a946bd1fd2b2b29eea582eea1d5 (opens in a new tab)