Osegi
Security·2 min read

NoisyTCP Linux bug can crash a server remotely, no login needed

NoisyTCP, a Linux kernel flaw hiding since 2015, lets an attacker crash a whole server over the network, even from inside a container.

A rack of servers in a data center with a red warning light on one machine, illustrating a Linux server crash.
Image: theregister

A bug that sat in the Linux kernel for 11 years can now knock servers offline from across the internet. It's called NoisyTCP, tracked as CVE-2026-99288, and an attacker doesn't need a password to use it.

Security researcher Hyunwoo Kim found the flaw and patched it this year. He says it affects almost all Linux distributions and dates back to October 2015. Kim published the details on November 15, after the disclosure embargo ended.

The problem sits in the kernel's TCP networking code. Two parts of the kernel can trip over each other while handling incoming traffic, and one ends up using memory that has already been freed. The result is a kernel panic, and the whole machine goes down.

Which servers are affected by NoisyTCP?

No special setup is needed. Nginx, Apache and SSH servers can be vulnerable out of the box. The attacker needs an open TCP port on a system that spreads incoming traffic across multiple receive queues or CPUs.

Containers don't help much. Because the bug is in the kernel, crashing a web server inside a container can take down the host and everything else on it.

In Kim's tests, Nginx, Apache and SSH servers on QEMU/KVM virtual machines fell over in between five seconds and two minutes. Bare metal was tougher: even with an exploit tailored to the target, crashing an Nginx server took about 14 hours.

Is there a fix for NoisyTCP?

A fix went into the upstream Linux kernel on November 3. Administrators still need to check whether their distribution has shipped an updated kernel. Red Hat rates the flaw Important with a CVSS score of 7.5.

For those who can't patch yet, Kim suggests two stopgaps: disable TCP SYN cookies, or limit incoming packet processing to a single receive queue. Both cost something. Turning off SYN cookies weakens protection against SYN flood attacks and has to be done separately for containers with their own network namespaces. Limiting packet processing can hurt network performance.

There's no evidence so far that NoisyTCP can steal data or take over a machine. Kim found a second path involving use-after-free memory, but it's much harder, and he has only built a limited lab exploit against virtual machines. The confirmed impact is remote denial of service.

Kim also found Dirty Frag in May, a kernel bug that let local users gain root.

Apps worth a look

SUMO: the number puzzle

Tap the right tiles, add them up, hit the target. Easy to learn, hard to master. Free, for all ages.

Tags:linuxnoisytcpcve-2026-99288kernelvulnerabilityhyunwoo kim

More from this day

See all →

More in: Security

See all →