# NoisyTCP: a remote Linux crash bug that sat in the kernel since 2015

> CVE-2026-99288 lets anyone who can reach an open TCP port crash a Linux host, even from inside a container. A fix landed upstream on 3 November.

Published 2026-11-16T18:30:00.000Z · Security · https://ihos.eu/noisytcp-linux-remote-crash/

Source: [NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making](https://www.theregister.com/security/2026/11/16/noisytcp-bug-gives-linux-servers-a-remote-crash-problem-11-years-in-the-making/5310144)

The researcher Hyunwoo Kim, who reported the Dirty Frag kernel bug earlier this year, has published another Linux flaw. Tracked as CVE-2026-99288 and named NoisyTCP, it sits in the kernel’s TCP code and dates from October 2015. Two parts of the kernel can race while handling incoming traffic, and one can end up using memory that has already been freed. The result can be a kernel panic.

According to The Register, an attacker needs no credentials, only access to an open TCP port on a system that spreads incoming traffic across several receive queues or CPUs. No special configuration is required: Nginx, Apache and SSH are affected in their defaults. In tests on QEMU/KVM virtual machines, Kim crashed them in between five seconds and two minutes. Bare metal was harder: after tailoring the exploit to the target, a crash of a server running Nginx took about 14 hours.

Kim describes a second path through the use-after-free that could in principle go further, and says he has a limited exploit against virtual machines in a lab. He has not shown general remote code execution, so the confirmed impact is remote denial of service. The details were published on 15 November after the embargo ended, and the fix was committed upstream on 3 November.

