CVE-2026-99288: NoisyTCP
NoisyTCP is a race condition in the Linux kernel TCP networking subsystem, introduced in Linux 4.4. Lockless established-socket lookups use SLAB_TYPESAFE_BY_RCU caches, allowing socket memory to be recycled while readers retain its address. After acquiring a reference, __inet_lookup_established() and __inet6_lookup_established() revalidate the connection tuple without checking hash membership. A stale lookup can therefore return a replacement socket occupying the same address with the same tuple while it remains unhashed. In the demonstrated SYN-cookie path, the replacement request socket has a NULL rsk_listener, which tcp_v4_rcv() dereferences, causing a kernel panic. Unauthenticated remote attackers can trigger the race through crafted traffic to a reachable TCP listener.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation causes host-wide denial of service through a kernel panic, interrupting all applications and containers sharing the affected kernel. Default-configured web servers, SSH servers, and other TCP listeners can expose the vulnerable kernel path. A separate, harder-to-trigger child-socket race can cause a use-after-free, but general-purpose remote code execution, data theft, and privilege escalation have not been demonstrated. Exploitation timing is environment-dependent: reported laboratory crashes ranged from seconds or minutes on virtual machines to approximately 14 hours on a quiet bare-metal server.
Mitigation
If you can’t patch tonight, do this now.
Temporarily setting net.ipv4.tcp_syncookies=0 blocks the demonstrated SYN-cookie request-reconstruction path, but does not remove the underlying race or cover the separate child-socket use-after-free variant. Apply this setting separately in every relevant network namespace, including container namespaces; newly created namespaces also require attention. Disabling SYN cookies weakens SYN-flood protection. Alternatively, serialize receive processing by configuring one receive queue on externally reachable interfaces and disabling Receive Packet Steering and Receive Flow Steering. This can substantially reduce throughput, may not be supported by every interface, and must remain effective after reboot or interface reconfiguration. Restrict unnecessary TCP exposure while awaiting patch deployment.
Remediation
Patch, then assume compromise.
Install a vendor-supported kernel update explicitly addressing CVE-2026-99288, reboot into it, and verify the running kernel. Upstream releases containing the primary correction include 6.12.117, 6.18.63, 7.3.4, and 7.4-rc2; distribution backports require checking vendor advisories rather than relying solely on upstream version comparisons. Debian 13 includes the correction in linux 6.12.117-1. The correction rejects unhashed sockets after reference acquisition, releases the reference, and restarts the lookup. It also replaces direct request-socket frees with reqsk_put() in affected SYN-cookie, Fast Open, and request-migration failure paths.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.
References
Frequently asked questions
- Is CVE-2026-99288 exploited in the wild?
- As of Nov 18, 2026, Mallory has no reports of CVE-2026-99288 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-99288?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-99288, the earliest disclosed Nov 16, 2026.
- Is there a patch for CVE-2026-99288?
- Install a vendor-supported kernel update explicitly addressing CVE-2026-99288, reboot into it, and verify the running kernel. Upstream releases containing the primary correction include 6.12.117, 6.18.63, 7.3.4, and 7.4-rc2; distribution backports require checking vendor advisories rather than relying solely on upstream version comparisons.
- How severe is CVE-2026-99288?
- CVE-2026-99288 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 0.16% (5th percentile) as of Nov 18, 2026.
Recent activity
127 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.