PoC Monitor
← All CVEs
CVE-2026-99288published 10 Nov 2026 18:19 UTCData: JSON · API

Linux

inet: reject unhashed sockets during established lookups

In the Linux kernel, the following vulnerability has been resolved: inet: reject unhashed sockets during established lookups TCP established ehash lookups are lockless. The socket caches involved use SLAB_TYPESAFE_BY_RCU, so memory can be reused before an RCU reader that retained its old address has finished. After a tuple match, __inet_lookup_established() and __inet6_lookup_established() acquire a reference and repeat the tuple check. They do not check whether the new object is hashed. If the address is reused for a socket with the same tuple, the lookup can acquire a reference to the new object and return it while its nulls node is unhashed. A PoC that drives reuse with a SYN cookie request socket reproduced the crash. The new request socket is unhashed and has a NULL rsk_listener. A lookup that had loaded the address of the old request socket acquired the reference published by tcp_get_cookie_sock() and returned the new object. tcp_v4_rcv() then read sk_state through the NULL listener. The resulting crash was: BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page ... Oops: Oops: 0000 [#1] SMP NOPTI CPU: 4 UID: 0 PID: 0 Comm: swapper/4 Not tainted 7.3.0-00591-g0e135910deec #1 PREEMPT(lazy) ... RIP: 0010:tcp_v4_rcv+0x44e/0x1280 ... R10: 0000000000000001 R11: 00000000024ca8c0 R12: 0000000000000000 ... CR2: 0000000000000012 CR3: 0000000103d50004 CR4: 0000000000770ef0 ... Call Trace: <IRQ> ? raw_local_deliver+0xae/0x240 ip_protocol_deliver_rcu+0x2d/0x180 ip_local_deliver_finish+0x84/0x100 ip_sublist_rcv_finish+0x5f/0x70 ip_sublist_rcv+0x12a/0x1d0 ip_list_rcv+0xfd/0x130 __netif_receive_skb_list_core+0x223/0x250 netif_receive_skb_list_internal+0x1d2/0x2c0 ? try_fill_recv+0x39/0x7b0 napi_complete_done+0x74/0x170 virtnet_poll+0x445/0x600 __napi_poll+0x27/0x1e0 net_rx_action+0x2fe/0x3b0 handle_softirqs+0xc2/0x2c0 __irq_exit_rcu+0x74/0xd0 common_interrupt+0x7f/0x90 </IRQ> ... Kernel panic - not syncing: Fatal exception in interrupt After taking a reference, check whether the nulls node is unhashed in both IPv4 and IPv6 established lookups. If it is unhashed or the tuple no longer matches, drop the reference and restart the lookup. Lookups racing with the TIME_WAIT hashdance, or with a request being replaced by its child, now restart and find the new socket instead of returning the old one. Request sockets that were never inserted into ehash can have a nonzero refcount, and a stale lookup can hold a transient reference. Therefore, when SYN cookie, Fast Open, and request migration paths fail after setting a nonzero refcount, release the references held by those paths with reqsk_put() instead of freeing the request directly.

First public PoC 5.7 daysafter publication · 16 Nov 2026
Public PoCs22 on GitHub
CVSS7.5high · scored by CNA · CWE-362
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 079096f103faca2dd87342cca6f23d4b34da8871, < d69100340b4cae08d40f898f1b601032403f6be6
  • >= 079096f103faca2dd87342cca6f23d4b34da8871, < 8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd
  • >= 079096f103faca2dd87342cca6f23d4b34da8871, < eb8a2d156f2c1d862fffdfd1b3432bfbcd939879
  • >= 079096f103faca2dd87342cca6f23d4b34da8871, < 4e2b3ef19e0e04adca38442f07dd6bc93c712bf1

Fixed in d69100340b4cae08d40f898f1b601032403f6be6, 8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd, eb8a2d156f2c1d862fffdfd1b3432bfbcd939879, 4e2b3ef19e0e04adca38442f07dd6bc93c712bf1

Linux Linux
  • 4.4

Fixed in 0, 6.12.117, 6.18.63, 7.3.4, 7.4-rc2

Mitigation

Upgrade Linux to d69100340b4cae08d40f898f1b601032403f6be6 or 8e5172cbd227fae32f3313cba1f3e1b9edb5c4fd or eb8a2d156f2c1d862fffdfd1b3432bfbcd939879 or 4e2b3ef19e0e04adca38442f07dd6bc93c712bf1 or later.

Upgrade Linux to 0 or 6.12.117 or 6.18.63 or 7.3.4 or 7.4-rc2 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published10 Nov 2026 · t = 0First public PoC16 Nov 2026 · t+5.7d

First public PoC 5.7 days after publication; not in CISA KEV. First PoC: h0rn3t/noisytcp-lab (created 16 Nov 2026, found by us: 19 Nov 2026).

PoC repositories

Found on GitHub.

2 PoCs · 2 pending · 1 informational

PoCs 2
RepositoryCreatedFound by usStarsAssessment
h0rn3t/noisytcp-lab 16 Nov 2026 +5.7 d 19 Nov 2026 5 PoC
tal7aouy/NoisyTCP 17 Nov 2026 +6.3 d 19 Nov 2026 0 PoC
Pending 2
RepositoryCreatedFound by usStarsAssessment
re4/noisytcp-poc 17 Nov 2026 +6.4 d 19 Nov 2026 6 Pending · listed by PoC Index; via PoC Index
mustafasaydam/CVE-2026-99288---NoisyTCP-Exploit 17 Nov 2026 +6.8 d 19 Nov 2026 0 Pending · listed by PoC Index; via PoC Index
Informational 1
RepositoryCreatedFound by usStarsAssessment
donxud/NoisyTCP-Blue-Team-Playbook 17 Nov 2026 +7 d 19 Nov 2026 0 Informational · detection
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.