Karen IT Security Response Center (KSRC) Advisory

Advisory ID: KSRC-2026-11171 | Publication Date: 17 November 2026

Linux Kernel TCP Race Condition Enabling Remote Denial of Service
CVE-2026-99288 (NoisyTCP)

Summary

A critical race condition in the Linux kernel’s TCP networking code allows a remote, unauthenticated attacker to trigger a kernel panic and crash the host. Tracked as CVE-2026-99288 and commonly referred to as NoisyTCP, the flaw was discovered and reported by security researcher Hyunwoo Kim (@v4bel).

The vulnerability has existed since Linux 4.4 (introduced in October 2015) and affects virtually all major Linux distributions until patched. Red Hat rates it as Important with a CVSS v3.1 score of 7.5. Confirmed impact is remote denial of service; reliable remote code execution has not been demonstrated.

Technical Overview

TCP established-socket lookups in the kernel are lockless. Under certain timing conditions involving SYN-cookie request sockets and concurrent packet processing across multiple receive queues (or with Receive Packet Steering enabled), a lookup can obtain a reference to a recycled but still-unhashed socket object. Subsequent access leads to a NULL pointer dereference and a kernel panic.

Because the flaw resides in the kernel networking stack, any host with a reachable TCP listener (default configurations of Nginx, Apache, OpenSSH, etc.) is a potential target. Crashing a service inside a container also takes down the underlying host. The attack requires no authentication and no special server configuration beyond ordinary listening ports.

Affected Systems

  • Linux kernel versions from 4.4 onward that do not contain the fix commit 4e2b3ef19e0e (“inet: reject unhashed sockets during established lookups”).
  • Virtually all major distributions that have not yet shipped a backported kernel.

Upstream fixed versions (examples):

  • 6.12.117
  • 6.18.63
  • 7.3.4

Distribution status varies. Some (e.g., certain Debian releases, Oracle UEK) have already published fixed packages; others (including many RHEL and Ubuntu branches as of mid-November 2026) are still rolling out updates. Administrators must verify the exact kernel package available for their platform.

Exploitation Status

  • Public disclosure around 15–16 November 2026 after the linux-distros embargo ended.
  • Researcher-provided technical write-up and limited proof-of-concept material exist.
  • On virtual machines the crash can often be triggered in seconds to a few minutes; on quiet bare-metal hosts it may take significantly longer.
  • No widespread in-the-wild exploitation confirmed as of this advisory’s publication.
  • Not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog at the time of writing.

Recommendations

  1. Immediate Action: Install a kernel that contains the fix (or the distribution’s equivalent backport) and reboot. Prioritize internet-facing hosts and container hosts.
  2. Inventory running kernels across the environment and map them to vendor advisories for CVE-2026-99288 / NoisyTCP.
  3. Where an immediate kernel update is not possible, apply temporary mitigations:
    • Disable TCP SYN cookies: sysctl -w net.ipv4.tcp_syncookies=0 (apply per network namespace / container as needed).
    • Reduce the number of receive queues on external interfaces to one and disable RPS/RFS where operationally acceptable.
  4. Monitor for unexpected kernel panics or system reboots on hosts that expose TCP listeners.
  5. Treat any host that experiences an unexplained panic after exposure to untrusted network traffic as potentially targeted; preserve logs and crash dumps where possible.
  6. Subscribe to your distribution’s security announcements so that subsequent kernel updates are applied promptly.

Given the extremely broad installed base of Linux servers and the fact that ordinary web and SSH services are sufficient targets, organizations should treat this as a high-priority kernel update for all internet-reachable and multi-tenant systems.

Support from KSRC

KSRC (Karen IT Security Response Center) is fully prepared to assist organizations with any questions, technical guidance, or incident-related issues arising from this vulnerability.

Whether you require help with kernel version assessment, upgrade planning, or response coordination, our team is available.


Karen IT
We make the Internet harder to abuse.