NLnet Labs fixed five CVEs in its recursive resolver five weeks after the September release that patched a critical one, so servers still on 1.26.1 are behind again. Debian shipped DSA-6581-1.
NoisyTCP: 11-year-old Linux flaw lets attackers crash servers
EditorialBy TrustList Editorial
CVE-2026-99288 needs no login and no special configuration, only a TCP port an attacker can reach. The fix went into the kernel on 3 November; two stopgaps exist for hosts that cannot take it yet.
- Linux
- Network Security
- Patch Management
- Vulnerability Management
About NoisyTCP: 11-year-old Linux flaw lets attackers crash servers
NoisyTCP: 11-year-old Linux flaw lets attackers crash servers
16 November 2026: A race condition in the Linux kernel's TCP code, tracked as CVE-2026-99288 and named NoisyTCP by the researcher who found and patched it, lets an attacker who is not logged in crash a server by sending packets to any listening TCP port. Red Hat rates it Important. The fix was merged into the kernel on 3 November, and the details became public on 16 November when the embargo agreed with Linux distributors ended.
Not yet independently verified. The technical account is the researcher's own, published on 16 November, and Red Hat's CVE record. We have not read each distribution's fixed package versions, and neither source reports attacks in the wild. We will update this when it can be confirmed, and remove this note.
A listening port is all it takes
Hyunwoo Kim, who reported the bug, says it can be triggered against what he calls plain TCP listeners: Nginx, Apache and SSH servers in their default configuration, with no unusual kernel option, firewall rule or socket type involved. The only condition is on the network card side. The machine must have two or more receive queues, or use Receive Packet Steering to spread packets across processors, which describes most servers and cloud instances.
The crash is a kernel panic, so it takes down the whole machine rather than one service. Kim points out the consequence for container hosts: an attack aimed at a web server inside a container stops the host and every other container on it. Red Hat's record describes the effect as an immediate operating system crash caused by an unauthenticated remote attacker, and classes the fault as a NULL pointer dereference.
Why the race is easier to win on virtual machines
The kernel looks up established TCP connections without taking a lock. NoisyTCP abuses the gap between two checks in that lookup: while one receive context is still holding the address of an old connection request, another frees it and builds a new SYN cookie request at the same memory address. The first context then picks up an object with no listener attached, and the receive path dereferences a NULL pointer.
How quickly that happens depends on timing noise. On QEMU/KVM virtual machines, where virtual processors can be preempted, Kim reports a crash within about five seconds to two minutes. Against Nginx on a quiet bare-metal server with eight receive queues it took about 14 hours, even with a proof of concept tuned for that machine. He also describes a second route that could give a remote use-after-free, and says it is hard to trigger because several races must succeed one inside another.
Eleven years of affected kernels
The bug arrived in a commit of 3 October 2015 and was fixed by commit 4e2b3ef19e0e on 3 November 2026, so it has been present for about 11 years and, in Kim's words, affects almost all Linux distributions. Red Hat's record carries the upstream patch title, "inet: reject unhashed sockets during established lookups", and a public date of 10 November. Each distribution ships the fix in its own kernel package, so the version to look for is in the vendor's advisory for CVE-2026-99288 rather than in a single number.
Two stopgaps, each with a cost
Applying the patched kernel is the priority. For hosts that cannot reboot yet, both sources give the same two temporary measures:
- Turn off SYN cookies with
sysctl -w net.ipv4.tcp_syncookies=0. The setting is per network namespace, so it has to be applied inside each container that has its own namespace, and it lowers the machine's protection against SYN floods. - Reduce the internet-facing interface to a single receive queue and disable RPS and RFS, which removes the concurrency the race needs at the price of network throughput.
Servers that sit behind a load balancer or proxy which terminates TCP are not reached directly by an attacker's packets; the balancer itself, if it runs Linux, is. Our patch management category lists the tools that track kernel updates across a fleet.
Sources
- Hyunwoo Kim: NoisyTCP, Linux Kernel TCP Pre-auth Remote Corruption (read 16 November 2026), 16 November 2026
- Red Hat Customer Portal: CVE-2026-99288, 10 November 2026
- BleepingComputer: New NoisyTCP Linux kernel flaw lets attackers crash servers, 16 November 2026
Categories & features
- Linux
- Network Security
- Patch Management
- Vulnerability Management
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
ISC's October release closes a GSS-TSIG replay that corrupts memory and three resolver crashes. No 9.18 build is listed, so 9.18 users must move to 9.20.30.
CVE-2026-119618 affects every release from 2.4.55 to 2.4.70 with HTTP/2 enabled, and the standalone mod_h2 module up to 2.0.42; two lesser flaws in mod_md and mod_vhost_alias are fixed too.
Release 3.0.20261105-3.0 changes trust stores across 12 packages, makes Python and Go reject the compromised intermediates, moves to kernel 6.6.161.1-1 and preserves SSL.com where needed.
CVE-2026-109518 abuses APT's handling of hard links when it follows redirects and retries downloads, which is on by default from Debian 12 and Ubuntu 22.04. Fixed packages shipped on 4 November.
Every Xen from 4.6 is affected and the advisory knows of no mitigation, only patches, which it lists for releases back to 4.17. Two more advisories, XSA-529 and XSA-530, are embargoed until 10 November.
Amazon Linux 2 and 2023 kernels are out now. EKS and ECS AMIs dated 31 October carry the fix, Redshift follows on 2 November and RDS and Aurora on 3 November.
A race in IPv4 TCP connection setup frees socket options too early. The kernel CVE team scores it 9.8, distributions 5.9 to 8.1; Debian has fixed kernels, Ubuntu lists fixes in progress.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More LinuxThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.