Skip to content

ήχος /ˈi.xos/ Greek for “sound”. We catch the signal in infrastructure news.

Security News For: engineers

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.

On this page · 1 min read
  1. Key takeaways
  2. Source
  3. What happened
  4. Why it matters
  5. What it means for you
  6. Sources

Key takeaways

  • 1NoisyTCP (CVE-2026-99288) is a use-after-free in the Linux TCP receive path that can panic the kernel, no login needed.
  • 2It affects almost all distributions, works against default Nginx, Apache and SSH, and a crash in a container takes down the host.
  • 3The upstream fix is from 3 November. Red Hat rates it Important (CVSS 7.5). Until you have a patched kernel, there are two unpleasant workarounds.

Original source · theregister.com

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

Published

What happened

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.

Why it matters

A denial of service without credentials is the kind of bug that gets scanned for quickly. Because the flaw is in the kernel, the usual container boundary does not help: the researcher reports that crashing a web server inside a container can bring down the host and everything else on it.

In one sentence:any Linux server with a reachable TCP port can be knocked over until its kernel is updated or a workaround is applied.

What it means for you

  • Check your distribution’s advisory for CVE-2026-99288 and schedule the kernel update plus a reboot.
  • Workaround one: disable TCP SYN cookies. This weakens SYN flood protection and must be set separately in containers with their own network namespaces.
  • Workaround two: restrict incoming packet processing to a single receive queue. This can reduce network performance.

Sources

  1. The Register — “NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making”, 16 Nov 2026

More in Security

All posts in this topic