Dev.to Security 🔐 Cybersecurity 👁 0 📖 1 min read

CVE-2026-99288 (NoisyTCP): What Every Linux Server Operator Needs to Know

There’s a race condition in the Linux kernel that’s been there since 2015. It crashes the kernel. No authentication required. The surface is your default Nginx, Apache, or SSH listener. It was fixed on November 3, 2026.

There’s a race condition in the Linux kernel that’s been there since 2015. It crashes the kernel. No authentication required. The surface is your default Nginx, Apache, or SSH listener.

It was fixed on November 3, 2026. That’s about eleven years after it was introduced.

What it is

CVE-2026-99288, named NoisyTCP by researcher Hyunwoo Kim (@v4bel), is a CWE-362 race condition in the TCP established-socket lookup path. The short version: a stale lookup can land on a reallocated request socket with a NULL listener. The kernel dereferences it. Panic.

Who’s exposed

Almost every Linux system running kernel 4.4 through 6.12.116 / 6.18.62 / 7.3.3. The race requires concurrent receive contexts — multi-queue NICs or RPS enabled. That’s the default on any modern server or cloud instance.

Three things that won’t save you

Your container — kernel is shared, panic takes the whole host
Your VM — vCPU preemption widens the race, crash lands in under 2 minutes vs ~14 hours on quiet bare metal
Waiting for CVSS — CNA hasn’t scored it yet; the host still goes down

What to do

Patch to a kernel with commit 4e2b3ef19e0e:

6.12.117
6.18.63
7.3.4
7.4-rc2

Full analysis — trigger flows, ABA race mechanics, container blast radius, detection indicators, distro-specific package versions:

https://threataft.com/articles/cve-2026-99288-noisytcp-linux-kernel-race-condition

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.