A race condition in the Linux kernel’s TCP code lets a remote attacker crash a server without logging in. Red Hat rates the flaw, CVE-2026-99288, Important, and Debian has published fixed kernels for its bookworm and trixie releases.
According to Red Hat’s CVE page, recycled socket memory can be accessed during lockless socket lookups before it is properly initialized and hashed. An attacker who generates network traffic that drives socket reuse can trigger a NULL pointer dereference and a kernel crash. Red Hat says the resulting kernel panic disrupts host availability and “does not allow data alteration or arbitrary code execution”. Its preliminary CVSS base score is 7.5. Debian’s tracker ties the flaw to the name NoisyTCP.
The exposure is broad. Red Hat says TCP networking is universally enabled in standard Red Hat Enterprise Linux deployments, “making any system with active network listeners susceptible”. A web server, a database port and an SSH daemon are all network listeners.
Debian’s security tracker lists fixed kernels: 6.1.192-1 for bookworm (DLA-4906-1), 6.12.117-1 for trixie (DSA-6628-1) and 7.3.4-1 in unstable. It still lists forky’s 7.2.15-1 as vulnerable. For hosts that cannot be patched yet, Red Hat gives two mitigations. The first is disabling SYN cookies, which it warns lowers protection against SYN floods and has to be applied in each container that uses a separate network namespace. The second is reducing the interface that receives external packets to a single receive queue, with RPS and RFS disabled.
In our reading, both mitigations take away something a production host needs, flood protection in one case and parallel packet processing in the other, so they suit only the short gap before a reboot window. Availability flaws often get scheduled behind code execution bugs. For a load balancer, a bastion host or a database server, a remote crash is the outage itself. Put those hosts first in the kernel rollout, alongside this month’s Apache HTTP Server 2.4.71 and PostgreSQL updates.
Source: Red Hat, CVE-2026-99288