NoisyTCP flaw lets remote attackers crash Linux servers

NoisyTCP flaw lets remote attackers crash Linux servers

Add CyberWorldOpsto your preferred sources on Google
NoisyTCP flaw lets remote attackers crash Linux servers
Vulnerabilities

Illustrative image generated with AI

A Linux kernel TCP flaw allows unauthenticated remote attackers to crash network-facing systems, Red Hat’s advisory warns. Tracked as CVE-2026-99288 and dubbed NoisyTCP, the vulnerability causes a kernel panic that takes down the host. A kernel patch is available, with temporary mitigations that change how servers handle incoming traffic.

BleepingComputer reported on November 16 that the 11-year-old flaw affects almost all Linux distributions, including systems running Nginx, Apache and SSH servers in default configurations. Red Hat describes standard Red Hat Enterprise Linux deployments with active network listeners as susceptible to traffic that repeatedly drives socket reuse.

The consequence is loss of availability. Red Hat explicitly says the flaw does not allow data alteration or arbitrary code execution.

A race in TCP socket handling

The vulnerability sits in the kernel’s TCP networking subsystem. During lockless socket lookups, a race can expose recycled socket memory before it has been properly initialized and entered into the kernel’s socket lookup structure. An attacker can generate traffic that drives socket reuse, triggering a NULL pointer dereference and crashing the operating system.

Researcher Hyunwoo Kim, who discovered the flaw, told BleepingComputer that exploitation uses crafted TCP packets to target the timing between SYN cookie handling and socket hashing. His description covers Linux systems that receive TCP packets directly and run Nginx, Apache or an SSH server.

Successful exploitation requires concurrent packet processing. A stale lookup in the kernel’s established-socket hash table must overlap with the freeing and reallocation of an existing request socket in different receive, or RX, contexts. Kim said differences in receive hashing between IPv4 fragments and ordinary TCP packets let attackers spread processing across those contexts.

That makes the relevant configurations servers with at least two RX queues, or systems where Receive Packet Steering (RPS) distributes packets across multiple CPUs. Kim cautioned that the race window is narrow, so triggering a crash on a quiet bare-metal server can take a long time.

Red Hat rates the vulnerability as Important and lists a preliminary CVSS v3.1 score of 7.5. Its scoring table lists low privileges and high confidentiality and integrity impacts, while its technical statement describes an unauthenticated attack limited to availability. The advisory’s technical description is explicit about the crash mechanism and its consequences.

Patch and temporary mitigations

BleepingComputer reported that a fix had entered the mainline Linux kernel two weeks before its November 16 article. Red Hat’s advisory also links kernel fixes. Neither document identifies concrete fixed distribution releases or kernel package versions.

For administrators who cannot immediately apply a fix or upgrade, Red Hat describes two mitigation measures:

  • Disable SYN cookies with sudo sysctl -w net.ipv4.tcp_syncookies=0. This blocks the path that reconstructs a request socket through a SYN cookie. The setting applies per network namespace, so it must also be applied in each container using a separate network namespace. Disabling SYN cookies reduces protection against SYN flood attacks.
  • Serialize incoming processing to one RX queue. Reduce the interface receiving external packets to a single RX queue and disable RPS and Receive Flow Steering (RFS). Red Hat says this can block the concurrent processing required for the race.

Kim also disclosed the Dirty Frag Linux privilege-escalation flaws in May and the Januscape virtual-machine escape vulnerability in July.

Administrators responsible for exposed Linux listeners should apply the available kernel fix. Where an immediate update is impractical, use Red Hat’s temporary measures, accounting for container network namespaces and the loss of SYN flood protection when disabling SYN cookies.

Security dossiers

Read next

Sources

CVEs covered in this article

Back to home

Latest Cybersecurity News

All cybersecurity news →