Security News

NoisyTCP: An 11-Year-Old Linux Kernel Flaw Lets Attackers Crash Servers Without a Password

The Register · 17 Nov 2026
Key Takeaway Check with your Linux vendor or hosting provider that a kernel update for CVE-2026-99288 is installed and the servers are rebooted onto it.

Security researcher Hyunwoo Kim has disclosed a Linux kernel flaw, tracked as CVE-2026-99288 and dubbed NoisyTCP, that lets attackers crash a server remotely without any credentials. Kim says it affects almost all Linux distributions. The bug dates back to October 2015 and went unnoticed until this year, when Kim found and patched it.

The problem sits in the kernel's TCP networking code. Two parts of the kernel can trip over each other while handling incoming traffic, so one ends up using memory that has already been freed. The result can be a kernel panic that takes down the whole machine. No special configuration is needed: services such as Nginx, Apache and SSH can be vulnerable out of the box. An attacker only needs access to an open TCP port on a system that processes traffic across multiple receive queues or CPUs.

Containers offer no protection here. Because the flaw is in the kernel, crashing a web server inside a container can bring down the underlying host and everything else on it. In testing against QEMU/KVM virtual machines, Kim crashed Nginx, Apache and SSH servers in between five seconds and two minutes. Bare-metal hardware was harder: even with an exploit tailored to the target, a crash of an Nginx server took roughly 14 hours.

The confirmed impact is denial of service. Kim has built a limited exploit for virtual machines in a lab and identified a second, much harder, use-after-free exploitation path, but has not shown general remote code execution. A fix was committed upstream on November 3, and Red Hat rates the flaw Important with a CVSS score of 7.5. Administrators must check whether their distribution has shipped an updated kernel. Two temporary workarounds exist: disabling TCP SYN cookies or limiting packet processing to a single receive queue. Both carry costs, including weaker SYN flood protection and reduced network performance.

Why it matters

Anyone running internet-facing Linux services, especially on virtual machines or shared container hosts, is exposed, because a single open TCP port is enough to take down the whole host and every workload on it. This breaks the assumption that container isolation limits the blast radius of an attack on one service. The workarounds also force a trade-off between SYN flood resilience and performance, and the SYN cookie change must be applied separately in containers with their own network namespaces.

What to do

  • Check whether your Linux distribution has released a kernel containing the upstream fix committed on November 3.
  • Apply the updated kernel to internet-facing servers and virtual machine hosts first.
  • Consider restricting incoming packet processing to a single receive queue if you cannot patch immediately, and weigh the performance cost.
  • Apply any SYN cookie workaround separately inside containers that use their own network namespaces.
Linux CVE-2026-99288 NoisyTCP denial of service containers kernel vulnerability

Summarised by CISO AI from The Register, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.