Information has been revealed about a vulnerability (CVE-2026-99288) in the Linux kernel's TCP stack, codenamed NoisyTCP, which leads to null pointer dereferencing or accessing freed memory due to a race condition during multi-threaded processing of a series of incoming SYN requests interspersed with fragmented IPv4 packets. This forces the kernel to distribute the processing of a single connection across multiple receive (RX) queues. The vulnerability can be exploited to cause a denial of service (putting the kernel into a panic state) by sending a specially crafted stream of TCP packets to server processes accepting TCP connections, such as http and ssh servers. While remote code execution exploitation is theoretically not ruled out, attempts to create a prototype universal exploit have not yet been successful, and performing an RCE attack outside laboratory conditions has not been achieved.
Working examples of denial of service attack execution have been demonstrated for Nginx, Apache httpd, and SSH in their default configurations. The vulnerability can be used to launch attacks on container isolation platforms, as exploiting the vulnerability in any container results in the shutdown of the entire system. serverDuring testing in virtual machine based on QEMU/KVM, exploitation took between 5 seconds to 2 minutes, but an attack on an Nginx server running on the host system, using 8 RX queues, took 14 hours.
The vulnerability has been present since Linux kernel 4.3 (2015) and has been fixed in releases 6.12.117, 6.18.63, and 7.3.4. The status of vulnerability patches in distributions can be assessed on these pages: Debian, Ubuntu, SUSE/openSUSE, RHEL, Gentoo, Arch,
Fedora.
The issue arises when using multiple RX queues (by default, you can check this via "ls /sys/class/net/interface_name/queues") or when enabling the RPS (Receive Packet Steering) mode (you can check this with "cat /sys/class/net/interface_name/queues/rx-*/rps_cpus"). As workarounds for blocking the vulnerability, it is suggested to use only one receive packet queue (RX) or to disable SYN Cookies ("sysctl -w net.ipv4.tcp_syncookies=0"), which will lead to decreased performance due to processing all incoming packets on a single CPU core and disabling protection against SYN flood attacks, respectively. Changing SYN Cookie settings is required for all namespaces (for each container).
Source: opennet.ru
