The NoisyTCP flaw in the Linux kernel can let a remote attacker crash an entire server without signing in. Security researcher Hyunwoo Kim found the 11-year-old bug in networking code shared by most Linux distributions, and kernel developers have merged a fix.

The vulnerability, tracked as CVE-2026-99288, can affect servers running Nginx, Apache or SSH with their default settings. These services rely on the kernel to handle incoming TCP connections. If the kernel crashes while processing network traffic, every service on the host can go offline, including applications unrelated to the original connection.

Why a network error can stop the whole server

The NoisyTCP flaw involves how the kernel reuses memory for network connections. According to Red Hat’s security team, one part of the kernel can try to use that memory before another part finishes preparing it. The resulting error can trigger a kernel panic, which brings the operating system to a halt.

That timing matters in practice. Kim said it could take a long time to trigger the fault on a quiet physical server because the operations must overlap within a narrow window. His findings concern machines that receive TCP traffic directly. Running one of the affected services therefore does not, on its own, establish how readily an attacker could crash a particular host.

The documented impact is a denial of service. A successful attack interrupts access to the machine, but the flaw does not give the attacker access to an account, the ability to modify stored data or a way to run code on the server.

The fix belongs in the Linux kernel

Linux developers merged a fix into the mainline kernel roughly two weeks before the November 16 report. For administrators, the relevant update is the kernel package supplied by their Linux distribution. Updating Nginx, Apache or an SSH server alone leaves the underlying networking code unchanged.

Administrators can use CVE-2026-99288 to check their distribution’s security tracker for the affected packages and the version containing the fix. The distinction matters for machines that run several workloads. On those hosts, patching the NoisyTCP flaw protects both the service receiving incoming connections and the other applications that depend on the same kernel.


0 responses to “NoisyTCP flaw can crash Linux servers without a login”