# NoisyTCP bug gives Linux servers a remote crash problem 11 years in the making Flaw can take down an entire host, even when the vulnerable service is running inside a container The researcher who sounded the alarm over Dirty Frag earlier this year has uncovered another Linux kernel flaw, and this one lets attackers crash entire servers remotely without so much as a password. The vulnerability, tracked as CVE-2026-99288 and dubbed NoisyTCP, was discovered by security researcher Hyunwoo Kim, who says it affects almost all Linux distributions. The flaw dates back to October 2015 and went unnoticed until this year, when Kim found and patched it. Attackers don't need to log in or get their hands on any credentials to cause trouble. They can simply knock the server over, although there's no evidence yet that the flaw can be used to steal data or hijack a machine. REG AD The bug is buried in Linux's TCP networking code. Two parts of the kernel can trip over each other while processing incoming traffic, leaving one trying to use memory that's already been freed. When that happens, Linux can panic and take the whole machine down with it. REG AD Kim says there's no need for any special ser
- Tracked as CVE-2026-99288.
- Key components named in the report: Linux kernel, nginx, ARM.
What happened
“Flaw can take down an entire host, even when the vulnerable service is running inside a container”
The researcher who sounded the alarm over Dirty Frag earlier this year has uncovered another Linux kernel flaw, and this one lets attackers crash entire servers remotely without so much as a password.
The vulnerability, tracked as CVE-2026-99288 and dubbed NoisyTCP, was discovered by security researcher Hyunwoo Kim, who says it affects almost all Linux distributions. The flaw dates back to October 2015 and went unnoticed until this year, when Kim found and patched it.
Why it matters
Linux runs a large share of the internet's servers, business infrastructure, and personal computers. A flaw that can be exploited in the kernel, OpenSSH, or another core component reaches far beyond one distribution, so the practical question is whether your systems are exposed and how quickly a tested fix is available.
What to do
- Review SSH exposure first: restrict access and watch authentication logs.
- Check the official advisory for the affected versions and fixed versions.
- Apply the vendor update after a normal backup and a short test where possible.
- If a patch is not available yet, use the mitigations in the advisory and reduce exposure.
Read the original
The full report, including versions, affected systems and any vendor statement, is at The Register. Kituwa summarizes the headline and adds practical context for people running Linux servers, desktops and small-business systems.



