NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making

Flaw can take down an entire host, even when the vulnerable service is running inside a container

The researcher who sounded the alarm over Dirty Frag earlier this year has uncovered another Linux kernel flaw, and this one lets attackers crash entire servers remotely without so much as a password.

The vulnerability, tracked as CVE-2026-99288 and dubbed NoisyTCP, was discovered by security researcher Hyunwoo Kim, who says it affects almost all Linux distributions. The flaw dates back to October 2015 and went unnoticed until this year, when Kim found and patched it.

Attackers don't need to log in or get their hands on any credentials to cause trouble. They can simply knock the server over, although there's no evidence yet that the flaw can be used to steal data or hijack a machine.

The bug is buried in Linux's TCP networking code. Two parts of the kernel can trip over each other while processing incoming traffic, leaving one trying to use memory that's already been freed. When that happens, Linux can panic and take the whole machine down with it.

Kim says there's no need for any special server configuration either. Services such as Nginx, Apache, and SSH can be vulnerable straight out of the box. An attacker needs access to an open TCP port on a system that processes incoming network traffic across multiple receive queues or CPUs.

Perhaps more concerning for administrators running containerized workloads, the damage isn't necessarily limited to the application being attacked. Because the flaw sits in the Linux kernel, crashing a web server inside a container can take down the underlying host and anything else running on it.

Kim found that the attack was particularly effective against virtual machines. During testing, he managed to crash Nginx, Apache, and SSH servers running on QEMU/KVM virtual machines in between five seconds and two minutes.

Physical hardware put up more of a fight. Even after tailoring his exploit to the target machine, Kim needed roughly 14 hours to crash a bare-metal server running Nginx.

Kim has a knack for finding holes in Linux. Back in May, he uncovered Dirty Frag, a kernel bug that allowed local users to gain root privileges. That one caused headaches for administrators when a working exploit went public before patches were ready.

His latest discovery, NoisyTCP, has another potentially nasty trick up its sleeve. Kim identified a second exploitation path involving a use-after-free condition, although pulling it off is considerably more difficult than simply crashing a server.

In his advisory, Kim says he has developed a limited exploit targeting virtual machines in a lab environment but has yet to demonstrate a general-purpose remote code execution attack. For the moment, the confirmed impact is remote denial of service.

A fix was committed to the upstream Linux kernel on November 3, but administrators will need to check whether their distribution has shipped an updated kernel. Red Hat has rated the vulnerability Important, assigning it a CVSS score of 7.5.

For those unable to patch immediately, Kim suggests two temporary workarounds: disabling TCP SYN cookies or restricting incoming packet processing to a single receive queue.

Neither is particularly appealing. Disabling SYN cookies reduces protection against SYN flood attacks, while limiting packet processing can hurt network performance. The former also needs to be applied separately to containers using their own network namespaces.

Kim published the details on November 15, once the disclosure embargo was lifted. The bug had been hiding in plain sight since 2015, leaving Linux servers vulnerable to remote crashes for 11 years. Not bad for a flaw that doesn't even require a login. ®

Original source NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making

Back to home