The flaw, CVE-2026-99288, is in the operating system's TCP networking code, not Agave itself. The Linux CVE record describes a race in which a connection lookup can pick up reused socket memory and crash the kernel. That puts the whole host's availability at risk, not just one application.
Hyunwoo Kim's advisory, written by the researcher who reported and patched the flaw, says it can be triggered remotely before login against reachable TCP services. It requires packet processing across at least two receive queues or multiple CPUs. In his technical write-up, Kim says he has only a limited, VM-specific lab exploit for remote code execution and is still researching a general-purpose exploit.
What Operators Should Do
Operators should check their distribution's security advisory to determine whether their running kernel is affected and upgrade to a patched kernel as soon as one is available, Anza said.
Where a patched kernel is unavailable, the temporary command published by Kim and Red Hat is:
``sh sudo sysctl -w net.ipv4.tcp_syncookies=0 ``
The change blocks the $SYN-cookie reconstruction path described in the advisory. It must be applied separately in each container using its own network namespace, and disabling $SYN cookies lowers protection against $SYN-flood attacks.
Anza instructed operators to restore $SYN cookies to their previous setting only after booting into a patched kernel. The no-validator-restart guidance applies to the temporary setting change, not to booting a replacement kernel.
Kernel Fixes Vary by Distribution
Anza's operator requirements say it builds and runs on Ubuntu 24.04. As of Nov. 16, Ubuntu's CVE tracker, last updated Nov. 11, marked the main linux package for Ubuntu 24.04 as 'Needs evaluation,' rather than listing a fixed version.
Debian's tracker lists fixed security updates for bookworm (linux 6.1.192-2) and trixie (linux 6.12.117-1). Red Hat's database still marks RHEL 8, 9 and 10 kernels 'Affected.' Red Hat rates the flaw 'Important,' with a preliminary CVSS severity score of 7.5.
NoisyTCP is distinct from CVE-2026-98432, covered earlier this month, which involved IPv4-option memory being freed while still in use. Patching that earlier flaw is not proof that a host is fixed for this one.