Newshot

Linux kernel vulnerability NoisyTCP, hidden for 11 years, exposed: sending specially crafted TCP packets can crash servers

AI summary

South Korean security researcher Hyunwoo Kim (Hyunwoo Kim) discovered a high-severity vulnerability in the Linux kernel, naming it NoisyTCP (CVE-2026-99288). The flaw has been latent for about 11 years; an attacker does not need to authenticate and only has to send specially crafted TCP packets to the target server to potentially trigger a Linux kernel crash, causing a denial of service (DoS). Kim published a technical report on the vulnerability on November 16. According to information posted to the Openwall security mailing list, the vulnerable code was first introduced into the Linux kernel on October 3, 2015, and a fix was not committed upstream until November 3, 2026. NoisyTCP stems from a race condition in the Linux kernel's TCP connection lookup process. When the kernel performs a lockless lookup in the hash table of established TCP connections, it may encounter socket memory that has already been freed and subsequently reallocated. If the new object happens to reuse the same memory address and connection information, the kernel may mistakenly acquire this new object. In one exploitation path disclosed by the researcher, an attacker can induce the kernel to access a request

Translation(model translation, not the source's own text)

Linux kernel vulnerability NoisyTCP, latent for 11 years, exposed: sending specially crafted TCP packets can crash servers

IT Home news on November 18: South Korean security researcher 金贤宇 (Hyunwoo Kim) has discovered a high-severity vulnerability in the Linux kernel and named it NoisyTCP (CVE-2026-99288).

The vulnerability has been latent for about 11 years. An attacker does not need to authenticate; they only need to send specially crafted TCP packets to the target server to potentially trigger a Linux kernel crash, causing a denial of service (DoS) on the server.

金贤宇 publicly disclosed the technical report on the vulnerability on November 16. According to information posted on the Openwall security mailing list, the code related to the vulnerability was first introduced into the Linux kernel on October 3, 2015, and a fix commit did not enter the kernel upstream until November 3, 2026.

The NoisyTCP issue stems from a race condition in the Linux kernel's TCP connection lookup process. When the kernel performs a lockless lookup in the hash table of established TCP connections, it may encounter Socket memory that has already been freed and subsequently reallocated. If the new object happens to reuse the same memory address and connection information, the kernel may incorrectly obtain this new object.

In one exploitation path disclosed by the researcher, an attacker can induce the kernel to access a request Socket that has no associated listener, ultimately triggering a NULL pointer dereference and causing a kernel crash.

金贤宇 pointed out that the vulnerability can affect common TCP services, and Linux servers running ordinary TCP services such as NGINX, Apache, and SSH may also be affected; no special application configuration is required.

However, exploitation also requires certain network conditions: the target server must have at least two RX (receive) queues, or have RPS (Receive Packet Steering) enabled, so that network packets can be distributed across multiple CPU processing contexts, thereby creating an opportunity to trigger the race.

According to the researcher's tests, in virtual machine environments such as QEMU / KVM, with the default configurations of NGINX, Apache, and SSH, triggering a kernel crash took about 5 seconds to 2 minutes. On a physical server equipped with 8 RX queues and under low load, the researcher used a test program with timing tuned for that environment and took about 14 hours to successfully trigger it.

This means that although the vulnerability can be exploited remotely, the actual trigger time is affected by factors such as server hardware, network queues, and system load.

If the affected service runs in a container, because the vulnerability occurs in the Linux kernel network stack, triggering the crash may affect the entire host and other containers running on it, not just the target application.

At present, the researcher has not demonstrated that the vulnerability can achieve privilege escalation or remote code execution, nor is there evidence that it can directly lead to data leakage. The main impact verified so far is remote denial of service.

IT Home notes that the remediation progress differs across Linux distributions. According to the Linux kernel stable release records, as of November 18, 2026, the relevant fixes have entered multiple stable kernel branches.

The upstream fixed versions include Linux Kernel 6.12.117, 6.18.63, and 7.4.4, and the mainline development version has reached 7.4-rc2. Note that the latest versions published on the kernel official website on November 17 have been updated to 6.12.118, 6.18.64, and 7.3.5. Actual deployment should be based on the security updates provided by the distribution.

Regarding distributions, according to official security advisories from Debian, Ubuntu, Red Hat, and AlmaLinux:

  • The Debian 13 series has been fixed, with the fixed version being 6.12.117-1; the Debian 12 series has also been fixed, with the relevant security update version being 6.1.192-2.
  • Multiple supported Ubuntu versions are still marked as affected, including Ubuntu 22.04, 24.04, 26.04, and 26.10.
  • The Red Hat Enterprise Linux 8, 9, and 10 series are all marked as affected, and no corresponding fixed kernel has been released yet.
  • AlmaLinux has backported the relevant patches for the 8, 9, and 10 series, and the fixed kernels have entered the testing repository.

金贤宇 also published temporary mitigation measures on a GitHub page, including disabling SYN Cookies, or limiting the network interface receive queue to one and disabling RPS and RFS. However, disabling SYN Cookies reduces the server's ability to resist SYN Flood attacks, so these measures cannot replace official security patches.

For Linux server administrators, it is recommended to promptly check the security advisories of the distribution in use, install kernel updates containing the fix for CVE-2026-99288, and restart the system after updating so that the fix takes effect.

Related articles

  • Kylin OS launches the high-quality hardware certification system KHQL, covering both desktop and server platforms
  • Valve releases SteamOS 3.10.1 preview update for Steam Deck: fixes issues such as failure to launch Forza Horizon
  • Open source openEuler releases an operating system for Agentic Infra, with cumulative domestic installations expected to exceed 22 million
  • Steam client Beta update released: fixes missing game covers in offline mode and resolves failure to load custom Proton on Linux
  • Valve releases SteamOS 3.9.6 beta: upgrades to the Linux 7.2 kernel and adds preliminary hibernation support
  • The Linux version of the Steam client is officially upgraded to 64-bit, using the same independent runtime environment as games

The translation is machine-generated and individual terms may be off. Nothing is rewritten or cut; the original is authoritative.

Published by IT之家
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗