NoisyTCP (CVE-2026-99288): 11-year-old Linux kernel TCP race lets an unauthenticated remote attacker panic servers with plain TCP listeners such as Nginx, Apache and SSH; fix commit 4e2b3ef19e0e
Researcher Hyunwoo Kim (@v4bel), who reported and patched the flaw, has published the NoisyTCP advisory for CVE-2026-99288, a Linux kernel TCP pre-authentication remote corruption bug, after the linux-distros embargo ended.
Kim says a stale ehash lookup races with the freeing and reallocation of a request socket in a different RX context; packets are spread across CPUs by the receive-hash difference between IPv4 fragments and regular TCP packets, so the target needs two or more RX queues or RPS enabled. In the first trigger path the kernel dereferences a NULL listener and panics (remote denial of service); because the bug is in the kernel, a crash triggered against a containerised web server takes down the whole host.
A second path can cause a remote use-after-free but needs nested races and is generally hard to trigger. Kim says it can be triggered against plain TCP listeners, including Nginx, Apache and SSH servers in default configuration; on QEMU/KVM virtual machines triggering took about 5 seconds to 2 minutes, and on a quiet bare-metal Nginx server with 8 RX queues about 14 hours with a tuned proof of concept.
Kim says it is not a TCP RCE so far: he has written only a very limited, lab-specific exploit targeting VM servers. The bug was introduced in commit 079096f103fa (3 October 2015) and fixed in commit 4e2b3ef19e0e (3 November 2026); Kim says it affects almost all Linux distributions. (source: NoisyTCP advisory, GitHub)
- Product
- Linux kernel TCP stack (IPv4 TCP listeners)
- Versions
- Kernels from commit 079096f103fa (3 Oct 2015) until fix commit 4e2b3ef19e0e (3 Nov 2026), per the researcher; check your distribution's kernel advisory for fixed package versions
- CVSS
- not published in sources read
- Exploited in Australia?
- unknown
- Patch to
- Install a kernel that includes fix commit 4e2b3ef19e0e from your distribution. Researcher's temporary mitigations if you cannot patch yet: disable SYN cookies (sysctl -w net.ipv4.tcp_syncookies=0, per network namespace, so apply it in each container namespace; this lowers SYN-flood protection), or serialise to a single RX queue on the internet-facing interface and disable RPS and RFS.
