Skip to content- Sources: primary, discussion
- Summary: CVE-2026-99288, which researcher Hyunwoo Kim calls NoisyTCP, is a race during lockless socket lookups in which recycled request socket memory is read before it is initialized and hashed. Crafted traffic can cause a NULL pointer dereference and a kernel panic, though not code execution. Red Hat rates it Important and lists stable kernel fixes, and BleepingComputer reports the fix reached mainline about two weeks ago. Red Hat's mitigations are to set net.ipv4.tcp_syncookies=0 in each network namespace or to reduce the ingress interface to one RX queue with RPS and RFS turned off.
- Why it matters: Any Linux host that takes TCP traffic directly is exposed until it runs a patched kernel, so check your distribution's kernel updates and node image updates.
- Background: SYN cookies let a server answer a SYN flood without keeping state. The server encodes the connection details in the initial sequence number and rebuilds the request socket when the client's ACK arrives. The kernel finds sockets in its established hash table (ehash) under RCU, without locks, so a reader can briefly see an object that is being freed and reused. Exploitation needs the stale lookup and the reuse to run at the same moment on different CPUs, which is why multiple RX queues or RPS are a precondition.
- Follow-up: Distribution kernel packages and cloud node image updates carrying the fix.