Linux Kernel Flaw Lets Attackers Crash Servers Remotely
Researcher Hyunwoo Kim disclosed NoisyTCP, tracked as CVE-2026-99288, a high-severity flaw affecting default network configurations.
Updated on Nov. 16, 2026 in Cybersecurity

Security researcher Hyunwoo Kim disclosed NoisyTCP, a high-severity Linux kernel flaw tracked as CVE-2026-99288, which lets unauthenticated attackers remotely crash internet-facing servers running default network configurations. Fixes are included in Linux stable kernels 6.12.117, 6.18.63 and 7.3.4.
Why it matters
Because the flaw lets unauthenticated attackers take down exposed servers without logging in, any unpatched Linux system facing the internet is vulnerable to disruption. Administrators running affected kernels are urged to apply the stable releases that contain the fix.
The flaw is triggered by specially crafted packets that abuse SYN cookies, and it is exposed on systems with multiple receive (RX) queues or Receive Packet Steering (RPS) enabled. Red Hat rates it 7.5 out of 10, though the stub does not report a full exploitability assessment.
The players
Hyunwoo Kim
A security researcher who discovered and disclosed the NoisyTCP flaw and previously reported the Dirty Frag Linux privilege escalation flaw.
Red Hat
A major enterprise Linux vendor that rated the NoisyTCP flaw 7.5 out of 10 in severity.
The details
Kim found a race condition in how the kernel looks up TCP connections, a flaw that has existed in the Linux kernel since October 2015. Kim has also reported the earlier Dirty Frag local privilege escalation flaw this year.
Timeline
October 2015: NoisyTCP flaw first introduced into the Linux kernel.
November 16, 2026: NoisyTCP disclosure published.
Seasonal Patterns
Like the earlier Dirty Frag privilege escalation flaw Kim reported this year, NoisyTCP sits in the kernel's long-standing TCP connection-handling code. The Linux TCP stack has carried this exposure since October 2015, which places the fix in a recurring category of kernel networking vulnerabilities.
Administrators running default Linux network configurations on internet-facing servers need to update to kernel 6.12.117, 6.18.63 or 7.3.4 or later. Systems with multiple RX queues or RPS enabled face the highest exposure to remote crashes.
The takeaway
Patching Linux kernels promptly matters most for servers exposed to the internet, since unauthenticated remote crashes require no credentials to trigger. Checking your kernel version against the fixed stable releases is a quick step for any Linux administrator.
Further reading
Explore more Cybersecurity coverage on Wisevoter for related vulnerability disclosures.



