CVE-2026-99288

Published Nov 10, 2026

Last updated 11 hours ago

CVSS high 7.5
Linux Kernel

Overview

AI description

Automated description summarized from trusted sources.

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

Risk scores

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

Weaknesses

134c704f-9b21-4f2e-91b3-4a467353bcc0
CWE-362

Social media

Hype score is a measure of social media activity compared against trending CVEs from the past 12 months. Max score 100.

Hype score

19

  1. 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

  2. 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

  3. 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

  4. 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

  5. 运维太苦了。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

  6. 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

  7. 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

  8. NoisyTCP 😳 CVE-2026-99288 #tcp #linux #cve

    @Sikorski_arQ

    16 Nov 2026

    20 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  9. 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

  10. 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

  1. In the Linux kernel, the following vulnerability has been resolved: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done tipc_aead_decrypt() goes straight from tipc_bearer_hold(b) to crypto_aead_decrypt(req) without taking a reference on the netns, unlike the encrypt path. When crypto_aead_decrypt() is offloaded asynchronously (e.g. the SIMD aead wrapper queuing to cryptd), the cryptd worker runs tipc_aead_decrypt_done() later. If the bearer's netns is torn down in the meantime, cleanup_net() -> tipc_exit_net() -> tipc_crypto_stop() frees the per-netns tipc_crypto, and the completion then reads it: tipc_aead_decrypt_done() dereferences aead->crypto->stats and aead->crypto->net, and tipc_crypto_rcv_complete() dereferences aead->crypto->aead[] and the node table -- reading freed memory. Decoded KASAN splat (v7.1-rc7, CONFIG_KASAN_INLINE + TIPC + TIPC_CRYPTO): BUG: KASAN: slab-use-after-free in tipc_aead_decrypt_done (net/tipc/crypto.c:999) Read of size 8 at addr ffff8881056258a8 by task kworker/u16:2/51 Workqueue: events_unbound Call Trace: tipc_aead_decrypt_done (net/tipc/crypto.c:999) process_one_work (kernel/workqueue.c:3314) worker_thread (kernel/workqueue.c:3397 kernel/workqueue.c:3478) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158) ret_from_fork_asm (arch/x86/entry/entry_64.S:245) Allocated by task 169: __kasan_kmalloc (mm/kasan/common.c:398 mm/kasan/common.c:415) tipc_crypto_start (net/tipc/crypto.c:1502) tipc_init_net (net/tipc/core.c:72) ops_init (net/core/net_namespace.c:137) setup_net (net/core/net_namespace.c:446) copy_net_ns (net/core/net_namespace.c:579) create_new_namespaces (kernel/nsproxy.c:132) __x64_sys_unshare (kernel/fork.c:3316) do_syscall_64 (arch/x86/entry/syscall_64.c:63) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Freed by task 8: kfree (mm/slub.c:6566) tipc_exit_net (net/tipc/core.c:119) cleanup_net (net/core/net_namespace.c:704) process_one_work (kernel/workqueue.c:3314) kthread (kernel/kthread.c:436) This is the same class of bug that commit e279024617134 ("net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done") fixed for the encrypt side. The encrypt path takes maybe_get_net(aead->crypto->net) before crypto_aead_encrypt() and drops it with put_net() on the synchronous return paths and in tipc_aead_encrypt_done(); the -EINPROGRESS/-EBUSY return keeps the reference for the async callback to release. The decrypt path was left without the equivalent guard. Mirror the encrypt-side fix on the decrypt path: take a net reference before crypto_aead_decrypt() (failing with -ENODEV and the matching bearer put if it cannot be acquired), keep it across the -EINPROGRESS/-EBUSY async return, and drop it with put_net() on the synchronous success/error return and at the end of tipc_aead_decrypt_done(). Reproduced under KASAN on v7.1-rc7: a UDP bearer with a cluster key is flooded with crafted encrypted frames from an unknown peer (driving the cluster-key decrypt path) while the bearer's netns is repeatedly torn down. The completion must run asynchronously to outlive tipc_crypto_stop(); on x86 the stock aesni gcm(aes) now decrypts synchronously, so the async path was exercised via cryptd offload. The unguarded aead->crypto dereference in tipc_aead_decrypt_done() is the unpatched upstream path; tipc_aead_decrypt() still lacks maybe_get_net(aead->crypto->net), so the completion can outlive the free on any config where crypto_aead_decrypt() goes async. Found by 0sec automated security-research tooling (https://0sec.ai).•CVE-2026-63801