AI description
CVE-2026-99288, also known as "NoisyTCP," is a race condition vulnerability in the Linux kernel's TCP networking subsystem that was introduced in October 2015 and remained latent for 11 years. Discovered by security researcher Hyunwoo Kim, the flaw resides in the lockless socket lookup mechanism used during TCP connection handling. Because the lookup process does not use locks, recycled socket memory can be accessed before it is properly initialized and hashed. An attacker can exploit this timing window by sending a crafted sequence of TCP packets, causing a stale lookup to return an unhashed request socket (such as one reconstructed via a SYN cookie). This results in a NULL pointer dereference and a subsequent kernel panic, taking the host and any hosted containers offline. To trigger the vulnerability, the target server must process incoming packets concurrently across multiple CPUs, which requires a network configuration with two or more receive (RX) queues or Receive Packet Steering (RPS) enabled. The exploit can be launched remotely and without authentication against standard services with default configurations, such as SSH, Apache, or Nginx. While the flaw allows attackers to cause a denial of service, it does not facilitate data alteration or arbitrary code execution. Upstream Linux kernel developers have resolved the issue in versions 6.12.117, 6.18.63, and 7.3.4 by ensuring that lookups reject unhashed sockets.
- Description
- 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.
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- NVD status
- Received
CVSS 3.1
- Type
- Secondary
- Base score
- 7.5
- Impact score
- 3.6
- Exploitability score
- 3.9
- Vector string
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Severity
- HIGH
- 134c704f-9b21-4f2e-91b3-4a467353bcc0
- CWE-362
Hype score is a measure of social media activity compared against trending CVEs from the past 12 months. Max score 100.
- Hype score
19
While there's no RCE PoC yet for it, CVE-2026-99288 (NoisyTCP) looks *real* nasty. Similar class of bug as CVE-2026-98432 (the not-MPTCP bug) but their PoC doesn't require MPTCP at all. Patch your servers ASAP.
@TheBlueMatt
17 Nov 2026
16024 Impressions
10 Retweets
102 Likes
32 Bookmarks
5 Replies
2 Quotes
SANS Stormcast Tuesday, November 17th, 2026: LiteLLM/Starlette RCE Scans (CVE-2026-42271, CVE-2026-48710); Danfoss AK-SM800A RCEs; cyrus-sasl SRP Bypass (CVE-2026-129483); NoisyTCP (CVE-2026-99288) https://t.co/q8gPMtfa95 https://t.co/p5QVZ6bXmF
@sans_isc
17 Nov 2026
1746 Impressions
3 Retweets
4 Likes
0 Bookmarks
1 Reply
0 Quotes
NoisyTCP (CVE-2026-99288): 11-year-old Linux kernel bug lets attackers crash servers remotely https://t.co/7aFd5sXjTw
@DaveHawkinsX
16 Nov 2026
89 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
Hyunwoo Kim disclosed NoisyTCP (CVE-2026-99288), an 11-year race in Linux TCP ehash lookup that triggers kernel panic via request_sock reuse. Attack needs multiple RX queues or RPS; works against default @nginxorg, Apache and SSH. QEMU crashes in seconds, bare metal takes hours.
@WorldCyberNewsX
16 Nov 2026
61 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
运维太苦了。Linux Kernel 又炸了! @grok CVE-2026-99288 是不是影响范围又很广?类似CVE-2026-98432 一样
@thunderwang
16 Nov 2026
104 Impressions
0 Retweets
3 Likes
0 Bookmarks
4 Replies
0 Quotes
NoisyTCP 😳 CVE-2026-99288 ➡️ sysctl net.ipv4.tcp_syncookies=0 #tcp #linux #cve #noisytcp
@Sikorski_arqPL
16 Nov 2026
68 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
NoisyTCP 😳 CVE-2026-99288 ➡️ sysctl net.ipv4.tcp_syncookies=0 #tcp #linux #cve #noisytcp
@Sikorski_arQ
16 Nov 2026
33 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
NoisyTCP 😳 CVE-2026-99288 #tcp #linux #cve
@Sikorski_arQ
16 Nov 2026
20 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
RHEL8,9,10が対象。アップデートパッケージはまだと // CVE-2026-99288 - Red Hat Customer Portal https://t.co/zjBYqHqyrf
@w4yh
16 Nov 2026
137 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
NoisyTCP vulnerability CVE-2026-99288 lets remote attackers panic Linux kernel TCP servers pre-auth. Patch to 6.12.117, 6.18.63 or 7.3.4. #NoisyTCP #Linux #LinuxKernel #TCP #DoS #CVE #CyberSecurity #InfoSec https://t.co/CmiW3CTiuo
@Daily_CyberSec
16 Nov 2026
443 Impressions
1 Retweet
2 Likes
1 Bookmark
0 Replies
0 Quotes