Skip to main content

Key Takeaways

  • NoisyTCP, tracked as CVE-2026-99288, is a flaw in the Linux kernel's TCP networking code that lets a remote attacker crash a server without logging in, according to researcher Hyunwoo Kim's advisory of November 15, 2026.
  • Red Hat rates CVE-2026-99288 as Important, with a score of 7.5 out of 10, and says the flaw crashes the operating system but does not allow data alteration or arbitrary code execution.
  • The NoisyTCP bug was introduced into the Linux kernel on October 3, 2015, and fixed on November 3, 2026, according to Kim, and Linux stable kernels 6.12.117, 6.18.63, and 7.3.4 contain the fix, iTnews reported.
  • As of November 16, 2026, Debian listed fixed kernels for its bookworm and trixie releases, Red Hat listed Red Hat Enterprise Linux 8, 9, and 10 as affected with no fix released, and Ubuntu listed CVE-2026-99288 as needing evaluation on its supported releases.

What happened

Security researcher Hyunwoo Kim published an advisory for NoisyTCP, tracked as CVE-2026-99288, on the oss-security mailing list on November 15, 2026, after an embargo agreed with Linux distribution maintainers expired. Kim calls it a "pre-auth remote corruption" flaw in the TCP networking code of the Linux kernel, the core of the operating system.

The flaw lets an attacker crash a Linux server by sending it specially crafted network traffic, without logging in. "An unauthenticated remote attacker can trigger an immediate operating system crash across the network without requiring privileges," Red Hat said on its CVE page. The cause is a race condition, a timing problem, in how the kernel looks up TCP connections, iTnews reported.

The crash, a kernel panic, stops the whole machine rather than a single program. Kim wrote that when the flaw is triggered against a web server running in a container, it takes down the entire host as well.

Red Hat rates the flaw Important, with a score of 7.5 out of 10, and says it "does not allow data alteration or arbitrary code execution." Kim described a second route through the same bug that can corrupt memory, but said it is generally hard to trigger. Kim does not claim the flaw can be used to run code, iTnews reported.

The bug was introduced in a kernel change dated October 3, 2015, and had been in the Linux kernel for about 11 years, Kim wrote.

Who is affected

Kim wrote that NoisyTCP "affects almost all linux distributions." The attack works against ordinary TCP services that an attacker's traffic can reach directly, such as nginx, Apache, and SSH servers running their default configuration, according to the advisory.

The server also needs two or more receive (RX) queues, or receive packet steering (RPS) turned on, Kim wrote. Both features spread incoming packets across processor cores, iTnews explained.

How long an attack takes depends on where the server runs. In Kim's tests, default nginx, Apache, and SSH servers on QEMU/KVM virtual machines crashed after about 5 seconds to 2 minutes. A quiet bare-metal server running nginx took about 14 hours to crash, even with attack code tuned for that machine.

Red Hat lists the kernels of Red Hat Enterprise Linux (RHEL) 8, 9, and 10 and the operating system images of OpenShift Container Platform 4 and 5 as affected. RHEL 7 is not affected because the vulnerable code is not present, Red Hat said.

Fixes

The fix is dated November 3, 2026, in Kim's advisory, and was merged into the mainline Linux kernel about two weeks before the disclosure, BleepingComputer reported. Linux stable kernels 6.12.117, 6.18.63, and 7.3.4 contain the fix, iTnews reported.

Linux distributions ship their own kernel builds. As of November 16, 2026, their status differed:

  • •
    The Debian security tracker lists fixed kernel packages for bookworm (6.1.192-1), trixie (6.12.117-1), and the unstable release (7.3.4-1).
  • •
    Red Hat lists the RHEL 8, 9, and 10 kernels as affected, with no fix released.
  • •
    Ubuntu lists its linux kernel package on 26.10, 26.04 LTS, 24.04 LTS, and 22.04 LTS as "needs evaluation."

What organizations should do

Kim's advisory says applying the kernel patch is the priority. For systems that cannot be updated right away, Kim and Red Hat list two temporary mitigations.

The first is turning off SYN cookies, a defense against connection flooding attacks, according to iTnews. Linux manages the setting separately for each network namespace, so administrators have to change it in each container that has its own network, Kim and Red Hat said. Turning it off lowers protection against SYN flood attacks. iTnews noted that this workaround does not cover the second, harder-to-trigger memory corruption path.

The second is reducing the network interface that receives outside traffic to a single RX queue and turning off RPS and receive flow steering (RFS). Kim said this blocks the timing overlap that the attack needs.