Home / Blog / New NoisyTCP vulnerability lets attackers crash Linux…
Tech News

New NoisyTCP vulnerability lets attackers crash Linux servers

A patch has landed for NoisyTCP, an 11-year-old Linux kernel flaw tracked as CVE-2026-99288 that allows remote attackers to crash unpatched internet servers.

By Dillip Chowdary • Nov 16, 2026 • Source: BleepingComputer

New NoisyTCP vulnerability lets attackers crash Linux servers
Image: BleepingComputer

At a glance

Vulnerability
NoisyTCP (CVE-2026-99288)
Affected software
Linux kernel, Nginx, Apache, OpenSSH
Exploit impact
Remote denial of service via kernel panic
Patch status
Merged into mainline Linux kernel two weeks ago
Exploitation limit
No data alteration or arbitrary code execution

Linux systems operating standard web and remote administration services face remote denial of service crashes following the discovery of an eleven-year-old vulnerability dubbed NoisyTCP. Discovered by security researcher Hyunwoo Kim and designated as CVE-2026-99288, the pre-authenticated remote corruption weakness resides in the Linux kernel TCP networking subsystem, as detailed in BleepingComputer's report. Unauthenticated attackers can exploit the timing between SYN cookie processing and socket hashing by transmitting specially crafted TCP packets directly to exposed endpoints.

This analysis examines the root causes of socket memory reuse, multi-queue packet distribution requirements, patch availability, and temporary mitigations for system administrators. The report is intended for site reliability engineers, security teams, and network administrators responsible for operating public-facing Linux hosts running default network stacks. Organizations maintaining infrastructure across major distributions must evaluate their receive-side packet handling to prevent sudden kernel crashes.

01Remote denial of service on default servers

The vulnerability impacts almost all Linux distributions running default configurations alongside common internet-facing software such as Nginx, Apache, and OpenSSH. Attackers deliver malicious TCP packets that trigger a NULL pointer dereference inside the kernel networking stack, resulting in an immediate operating system crash. Because the flaw operates prior to authentication, any system accepting direct TCP connections can be forced into a kernel panic by an unauthorized remote party.

Kim determined that the flaw exposes systems without requiring credentials, administrative privileges, or previous session state. Internet services running standard socket listeners handle inbound handshakes through default kernel routines that fail to synchronize safely under specific network loads. While the weakness destabilizes the host operating system instantly, the underlying memory corruption does not expose stored data or permit arbitrary code execution.

02Lockless socket lookups and packet fragments

According to the Red Hat security team, the root failure originates from a race condition occurring during lockless socket lookups within the network subsystem. When the kernel handles rapid connection churn, recycled socket memory can be read before it has been completely initialized and hashed into the system tables. A remote attacker can engineer network traffic patterns that accelerate socket reuse, causing the uninitialized structure to trigger a fatal NULL pointer dereference.

Triggering the failure requires a stale established hash lookup alongside the simultaneous freeing and reallocation of an existing request socket across separate receive contexts. Attackers separate packet processing paths across CPU cores by exploiting the difference in receive hashes between IPv4 fragments and standard TCP packets. Consequently, the flaw primarily threatens hosts configured with two or more receive queues or platforms where Receive Packet Steering distributes traffic across multiple processor cores.

03Kernel panics without code execution access

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

Despite the severe disruption caused by host crashes, CVE-2026-99288 remains strictly a denial of service vulnerability. The flaw does not grant threat actors the ability to bypass access controls, run shell commands, or tamper with server data. Security analysts confirmed that while the kernel panic takes the operating system offline, the corrupting condition terminates the host before any executable memory manipulation can occur.

The window of opportunity required to win the timing race remains narrow under typical production environments. Kim pointed out that triggering the crash against a quiet bare-metal server can take a long time due to predictable packet dispatching. Attackers must maintain sustained, precisely staggered network streams to force concurrent execution across distinct receive queues on the targeted machine.

04Mainline kernel patches and queue serialization

A patch resolving CVE-2026-99288 was merged into the mainline Linux kernel two weeks ago and is rolling out to supported distribution channels. System administrators should prioritize applying updated kernel packages across all exposed production hosts to remediate the underlying lockless socket lookup flaw permanently. Because the fix addresses the core TCP subsystem race, updating the kernel eliminates the crash condition without modifying network hardware configurations.

For organizations unable to upgrade immediately, the researcher outlined two operational adjustments to disrupt the race condition:

  1. Disable SYN cookies turn off SYN cookie evaluation to eliminate the timing collision between cookie verification and socket hashing.
  2. Serialize receive queues restrict network traffic to a single RX queue to block multi-CPU concurrent processing.

Note: While disabling SYN cookies mitigates the race condition, the change lowers server resilience against high-volume SYN flood attacks. Administrators adopting temporary queue serialization must also weigh potential packet throughput reductions against the immediate risk of remote kernel crashes.

05Researcher track record across kernel flaws

Hyunwoo Kim has uncovered multiple high-impact flaws in the Linux kernel architecture during recent vulnerability research campaigns. In May, Kim disclosed Dirty Frag, a local privilege escalation chain combining an RxRPC weakness tracked as CVE-2026-43500 and an xfrm-ESP flaw tracked as CVE-2026-43284. That exploit chained page-cache write bugs to obtain root privileges across major distributions including Ubuntu, Red Hat Enterprise Linux, CentOS Stream, and Fedora.

In July, Kim disclosed Januscape, a sixteen-year-old vulnerability within the Linux kernel virtualization framework. That security weakness enabled unauthenticated attackers to escape virtual machine boundaries and execute arbitrary code on the underlying host operating system. The discovery of NoisyTCP highlights ongoing architectural risks within legacy kernel networking pathways that have persisted across more than a decade of active distribution releases.

Frequently asked questions

What is the NoisyTCP vulnerability in the Linux kernel?

NoisyTCP is an eleven-year-old pre-authenticated flaw tracked as CVE-2026-99288 in the Linux kernel TCP networking subsystem. It allows remote attackers to trigger a NULL pointer dereference and crash the operating system using crafted TCP packets.

Can attackers use CVE-2026-99288 to execute arbitrary code or steal data?

No, the vulnerability causes an immediate kernel panic resulting in denial of service. It does not allow threat actors to alter system data or gain arbitrary code execution.

What system setups are vulnerable to remote NoisyTCP exploitation?

Systems running default installations of Nginx, Apache, or SSH servers that process direct TCP traffic are affected. Successful exploitation requires servers with two or more RX queues or configurations where Receive Packet Steering distributes packets across multiple CPUs.

How can administrators mitigate NoisyTCP if kernel updates cannot be applied immediately?

Administrators can disable SYN cookies and serialize network traffic to a single RX queue to eliminate the race window. However, disabling SYN cookies lowers protection against SYN flood attacks.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →