NoisyTCP: 11-year-old Linux kernel TCP flaw (CVE-2026-99288) lets remote attackers crash servers via SYN cookie race
A Linux kernel NULL pointer dereference in the TCP subsystem, dubbed NoisyTCP (CVE-2026-99288), was disclosed by researcher Hyunwoo Kim. It has existed for 11 years and affects almost all Linux distributions. An unauthenticated remote attacker can send crafted TCP packets that exploit a race between SYN cookie handling and socket hashing, causing a kernel panic and denial of service on hosts running Nginx, Apache or SSH with default configurations. It does not allow data alteration or code execution. The race window is narrow, so triggering it against a quiet bare-metal server can take a long time. The article reports no exploitation in the wild. This article was based on the article alone; no web research was performed.
Entenda a falha
A vulnerabilidade
CVE-2026-99288, nicknamed NoisyTCP, is a NULL pointer dereference in the Linux kernel TCP subsystem that has existed for 11 years and affects almost all Linux distributions. An unauthenticated remote attacker who can send crafted TCP packets to a host running Nginx, Apache or SSH with default configuration can cause a kernel panic and denial of service. It does not allow data alteration or code execution. The race window is narrow, so a quiet bare-metal server can take a long time to trigger. Exploitation needs two or more RX queues, or RPS spreading packets across CPUs. The articles give no specific affected version ranges; a fix is merged in mainline Linux.
Como funciona
A remote client sends TCP packets to a listening service, and the kernel looks up sockets without taking locks. When SYN cookies are in play, a request socket can be freed and its memory reallocated while another CPU is still doing a stale lookup in the established-connections hash (ehash). Because the packets are processed in different RX contexts, the lookup can reach recycled socket memory before it has been properly initialized and hashed. The kernel then dereferences a NULL pointer and panics. Packets are spread across contexts by the different receive hash of IPv4 fragments versus regular TCP packets.
Por que é vulnerável
The root cause is a race condition in lockless socket lookups between SYN cookie handling and socket hashing: recycled socket memory can be used before it is initialized and hashed, with no safeguard against the stale lookup. The articles do not explain why it went unnoticed for 11 years, nor do they detail what the fix changes; they only say a fix was merged into mainline about two weeks before publication.
Como foi descoberta
The flaw was discovered and disclosed by security researcher Hyunwoo Kim, who also described the conditions needed to trigger it. Red Hat's security team published an analysis of the race condition. The articles do not say how or when it was reported to the kernel developers. A fix reached the mainline kernel about two weeks before the BleepingComputer report of 16 November 2026, and no exploitation in the wild is reported. Kim previously disclosed Dirty Frag and Januscape.
Explicação gerada por IA a partir da matéria e dos artigos, em 16/11/2026 08:15.
Detalhes técnicos
According to Red Hat, a race condition during lockless socket lookups lets recycled socket memory be accessed before it is initialized and hashed. Triggering it requires a stale ehash lookup to run concurrently with the freeing and reallocation of a request socket in different RX contexts. Packet processing is spread using the receive-hash difference between IPv4 fragments and regular TCP packets. Targets therefore need two or more RX queues, or RPS distributing packets across CPUs.
Remediação
A fix was merged into the mainline Linux kernel about two weeks before publication. Apply the patch or upgrade the kernel. If that is not possible, disable SYN cookies, which reduces SYN flood protection, and serialize to a single RX queue to block the race.
Linha do tempo
-
NoisyTCP: 11-year-old Linux kernel TCP flaw (CVE-2026-99288) lets remote attackers crash servers via SYN cookie race
ler a análise desta fonte ocultar
A Linux kernel NULL pointer dereference in the TCP subsystem, dubbed NoisyTCP (CVE-2026-99288), was disclosed by researcher Hyunwoo Kim. It has existed for 11 years and affects almost all Linux distributions. An unauthenticated remote attacker can send crafted TCP packets that exploit a race between SYN cookie handling and socket hashing, causing a kernel panic and denial of service on hosts running Nginx, Apache or SSH with default configurations. It does not allow data alteration or code execution. The race window is narrow, so triggering it against a quiet bare-metal server can take a long time. The article reports no exploitation in the wild. This article was based on the article alone; no web research was performed.
Technical Details
According to Red Hat, a race condition during lockless socket lookups lets recycled socket memory be accessed before it is initialized and hashed. Triggering it requires a stale ehash lookup to run concurrently with the freeing and reallocation of a request socket in different RX contexts. Packet processing is spread using the receive-hash difference between IPv4 fragments and regular TCP packets. Targets therefore need two or more RX queues, or RPS distributing packets across CPUs.
Remediation
A fix was merged into the mainline Linux kernel about two weeks before publication. Apply the patch or upgrade the kernel. If that is not possible, disable SYN cookies, which reduces SYN flood protection, and serialize to a single RX queue to block the race.