Research · 3 min read
A Linux bug called NoisyTCP can crash servers. Running code is not shown
Researcher Hyunwoo Kim says CVE-2026-99288 is an 11-year-old flaw in the kernel’s TCP code. A remote attacker can panic the machine. A patch is already in the mainline kernel.

An old bug in the Linux kernel can knock a server offline. The effect that is shown is a crash. Kim’s own note says running code is not a finished, general result: he describes only a limited lab case against virtual machines. BleepingComputer reported the finding on November 16, 2026. Researcher Hyunwoo Kim calls it NoisyTCP. The identifier is CVE-2026-99288.
What Kim and Red Hat say
Kim says the flaw has been in the kernel’s TCP code for about 11 years. It is a null-pointer crash. Someone who is not logged in can reach it with crafted TCP packets, by winning a race between the way the kernel handles SYN cookies and the way it looks up sockets. Red Hat’s description, quoted by BleepingComputer, says recycled socket memory can be used before it is initialized. The result is a kernel panic and the machine goes down.
Kim says the race is narrow. Against a quiet physical server it can take a long time to hit. He also says it applies to Linux systems that receive TCP packets directly and run Nginx, Apache or SSH with default settings, when packets are spread across more than one receive queue or more than one processor. BleepingComputer says the bug affects almost all distributions. Kim says the result he can show in general is a crash, and that a way to run code on ordinary servers is not done.
A patch exists. Kim says the fix was merged into the mainline kernel two weeks before the November 16 article. Distributions still have to ship it. For people who cannot update yet, he suggests turning SYN cookies off, which weakens protection against SYN floods, and forcing traffic onto a single receive queue so the race cannot line up. Those are tradeoffs, not a preference over the patch.
What you can do
- Install the kernel update from your distribution when it includes CVE-2026-99288, then reboot. A patched package that is not running does not help.
- If you cannot reboot yet, treat the two workarounds as temporary and write down that SYN cookies are off, so you turn them back on after the update.
- A crash is not, by itself, a sign that someone is on the machine. The published effect is the server going down. If it reboots and you also see new accounts or new processes, look for a different cause.
- If you only use a website, you do not patch its kernel. Nothing here asks you to change a password.
How Frame helps
Frame can also look up your verified emails in Have I Been Pwned’s breach database. This is a crash bug, not a list of personal addresses. Frame doesn’t scan servers.
Sources
- BleepingComputer, New NoisyTCP vulnerability lets attackers crash Linux servers, November 16, 2026, citing Hyunwoo Kim and Red Hat
- Hyunwoo Kim, NoisyTCP, the researcher’s note on what the bug has been shown to do
More stories
New posts, by email.
About once a month. Plain-language privacy notes, nothing else. I never share your address.


