Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
NoisyTCP — Security advisory for CVE-2026-99288, a Linux kernel TCP pre-auth race condition enabling remote denial of service, with trigger analysis, affected versions, and mitigations. | Kitploit
Tools/GitHubGitHub/v4bel/noisytcp
Vulnerability AnalysisExploitationNetwork SecurityPapers & Research
GitHubv4bel/noisytcp

NoisyTCP

Security advisory for CVE-2026-99288, a Linux kernel TCP pre-auth race condition enabling remote denial of service, with trigger analysis, affected versions, and mitigations.

View Repository
3873 days agoNot yet reviewed
Share

NoisyTCP: Linux Kernel TCP Pre-auth Remote Corruption (CVE-2026-99288)

Abstract

This report is a security advisory for the NoisyTCP (CVE-2026-99288) vulnerability reported and patched by Hyunwoo Kim (@v4bel). It is a Linux Kernel TCP Pre-auth Remote Corruption vulnerability.

To trigger this vulnerability, a stale ehash lookup and the freeing and reallocation of an existing request socket must proceed concurrently in different RX contexts. Packet processing has to be spread out by using the difference in receive hash between IPv4 fragments and regular TCP packets, so it can be triggered against servers that have two or more RX queues, or where RPS distributes packets across multiple CPUs.

That is, since this vulnerability can be triggered against "plain" TCP listeners, it can be triggered pre-auth and remotely against servers that TCP packets sent by an attacker can reach directly, such as Nginx, Apache, and SSH servers running with their "default" configuration.

[!NOTE] The embargo agreed upon after reporting this vulnerability to [email protected] has ended, so this NoisyTCP document is now being published.

Trigger Flows

There are two trigger flows for this vulnerability, and an attacker can arbitrarily choose either one to trigger it.

1. request_sock Reuse ABA Race

While a stale lookup has found an existing request socket, another RX context frees it and reallocates a SYN cookie request with the same tuple at the same slab address.

The stale lookup acquires a refcount on the new object and then even passes the tuple recheck, but the new request has no listener attached to it. After that, the TCP receive path dereferences the NULL listener, which causes a kernel panic.

In the end, a remote DoS can be triggered.

Because this is a Linux kernel TCP vulnerability, if the DoS is triggered against a web server running in a container, it takes down not only the web server application but the entire host.

2. Full child socket ABA Race

This path can trigger a remote use-after-free, but since complex race scenarios have to succeed in a nested way, it is generally hard to trigger without using special techniques.

Trigger Characteristics

To trigger this vulnerability, another RX context has to get in between the first tuple check and the refcount acquisition. Because of this, against bare-metal servers, especially quiet servers with little execution variance and contention, triggering the race can take a long time.

Against Nginx, Apache, and SSH servers running with their default configuration on VMs such as QEMU/KVM, where vCPU preemption can occur, it took about 5 seconds to 2 minutes to trigger.

Against Nginx running with its default configuration on a quiet bare-metal server (8 RX queues), it took about 14 hours to trigger, even though a PoC with race timing carefully tuned for the target environment was used.

Affected Versions

The affected range of NoisyTCP (CVE-2026-99288) is as follows.

  • Introduced: 079096f103fa (2015-10-03)
  • Fixed: 4e2b3ef19e0e (2026-11-03)

That is, this vulnerability had been latent in the Linux kernel for about "11 years" and affects almost all Linux distributions.

Mitigations

Applying the 4e2b3ef19e0e patch is the priority, but if it is difficult to apply it immediately, one of the following temporary mitigations can be used.

1. Disable SYN cookies

This blocks the path where a request socket is reconstructed through a SYN cookie. The default value of this setting is 1 on most Linux distributions.

sudo sysctl -w net.ipv4.tcp_syncookies=0

This setting is managed per network namespace. It has to be applied to "each" container that uses a separate network namespace. Disabling it lowers the protection against SYN floods.

2. Serialize to a single RX queue

This vulnerability requires different RX contexts to race concurrently. Reducing the RX queues of the interface where external packets come in to one and disabling RPS and RFS can block the race.

FAQ

1. Does the victim server need special configuration?

No. The race condition only needs a server with two or more RX queues, or with RPS enabled.

Many other bugs trigger only when a rarely used configuration, a netfilter rule or a specific socket is set up. This one triggers even when the server does nothing more than call listen().

Because of this, it can be triggered on any Linux server that receives the attacker's TCP packets directly, such as servers running Nginx, Apache, SSH or a Proxy.

That said, as described above, the race window is narrow, so triggering it against a quiet bare-metal server can take a long time.

2. So is this a TCP RCE?

Not yet. and basically, no. So far I have only written a very limited, lab-specific exploit that targets VM servers. I am still researching a general-purpose exploit.

But remote DoS can be achieved without much difficulty.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    806
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    523
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    441
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    270
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    264

Explore all tools

Browse our collection of tools

View all tools →