Protect.Computer
NEWS

NoisyTCP: Linux Kernel Flaw (CVE-2026-99288) Can Crash Servers

· 2 min read · Device safety Network safety
NoisyTCP: Linux Kernel Flaw (CVE-2026-99288) Can Crash Servers

A Linux kernel flaw nicknamed NoisyTCP, tracked as CVE-2026-99288, lets an unauthenticated remote attacker crash a server by sending specially crafted TCP packets, according to researcher Hyunwoo Kim, who found it. BleepingComputer reports that the bug is 11 years old and affects almost all Linux distributions. Kim’s write-up says the flaw dates to a 2015 change (commit 079096f103fa) and was fixed in mainline Linux on 3 November 2026 (commit 4e2b3ef19e0e).

The kernel commit message explains the cause as a race in how the kernel looks up TCP connections without locks: freed socket memory can be reused while another CPU is still reading the old address, so the kernel can end up dereferencing a NULL pointer and panic. Kim says this can be reached before any login, against plain TCP listeners such as Nginx, Apache or SSH servers in their default configuration, and that a server in a container goes down entirely, not just the application. BleepingComputer and Red Hat both say it causes a crash but does not let an attacker alter data or run code; Kim’s write-up describes a second, harder path that could lead to a use-after-free, and says it generally needs special techniques. Red Hat rates the flaw Important with a preliminary CVSS score of 7.5.

There is a practical limit. Kim says the race window is narrow, so triggering it against a quiet bare-metal server can take a long time, and the attack needs a server with two or more receive queues or one where receive packet steering spreads packets across CPUs.

How to check if you’re affected

Affected products are Linux servers whose kernel does not yet include the fix for CVE-2026-99288 (mainline commit 4e2b3ef19e0e), particularly those that accept TCP connections directly from untrusted networks.

  • Compare your kernel package version with your distribution’s tracker for CVE-2026-99288. Debian’s tracker lists the issue as fixed in bookworm (security) 6.1.192-2, trixie (security) 6.12.117-1 and unstable 7.3.4-1; Red Hat’s page for the CVE carries its own product status.
  • If you cannot update right away, Kim’s write-up lists two temporary mitigations. The first is disabling SYN cookies with sudo sysctl -w net.ipv4.tcp_syncookies=0; it is a per-network-namespace setting, so it must be applied in each container that has its own namespace, and it lowers protection against SYN floods. The second is reducing the interface that receives external packets to a single receive queue, which removes the cross-CPU race the attack needs.
  • Kim says applying the kernel patch is the priority; the mitigations are for systems where it cannot be applied immediately.

Sources

Related reading