Vulnerabilities
NoisyTCP flaw lets attackers crash Linux servers remotely
A newly revealed Linux vulnerability called NoisyTCP lets attackers crash servers running Nginx, Apache, or SSH. A patch is available, but most Linux systems are affected until updated.
Ross Grant3 min read

The short version
A bug called NoisyTCP has been found in Linux, the operating system that runs most web servers. This flaw lets attackers crash servers from afar, but they cannot steal data or take control. A fix is available, but many systems are still at risk until updated. If you run a Linux server, check for updates and apply them as soon as possible.
What happened?
A vulnerability called NoisyTCP (CVE-2026-99288) has been found in the Linux kernel. Attackers can crash Linux servers running Nginx, Apache, or SSH by sending specially crafted network traffic. A patch is available, but most Linux systems are affected until updated. Only BleepingComputer has reported this so far.
How the flaw works
A vulnerability called NoisyTCP (CVE-2026-99288) has been found in the Linux kernel’s TCP networking subsystem. According to BleepingComputer, the flaw is 11 years old and affects almost all Linux distributions. The issue is a NULL pointer dereference, which means the system tries to use memory that does not exist. This causes a kernel panic, which crashes the server.
The root cause is a race condition during lockless socket lookups. A race condition is when two parts of a program try to use the same resource at the same time, leading to unpredictable results. In this case, recycled socket memory can be accessed before it is properly set up. If an attacker sends specially crafted network traffic, they can trigger this bug and crash the server. However, the attack does not let them run code or change data on the system, only crash it (BleepingComputer (opens in a new tab)).
Who is affected
Any Linux system that receives TCP packets directly and runs Nginx, Apache, or an SSH server with default settings is at risk. This covers a large number of web servers and remote access systems. The researcher who found the flaw, Hyunwoo Kim, said that triggering the bug on a quiet, bare-metal server could take a long time, because the timing needed is very precise. Servers with two or more receive queues, or those using Receive Packet Steering (RPS) to distribute packets across CPUs, are more exposed.
The response
A patch for CVE-2026-99288 is already available and has been merged into the mainline Linux kernel. System administrators are advised to update their kernels as soon as possible. For those who cannot patch immediately, the researcher suggests two workarounds: disable SYN cookies (which lowers protection against SYN flood denial-of-service attacks) and limit the server to a single receive queue to block the race condition.
Has this happened before?
The same researcher, Hyunwoo Kim, has previously found other serious Linux kernel flaws. In May, he disclosed Dirty Frag, which allowed attackers to gain root access by chaining two other vulnerabilities. In July, he reported Januscape, a bug that let attackers escape from a virtual machine and run code on the host system. These discoveries show that old and complex code in the Linux kernel can hide critical bugs for years.
What you should do
If you manage Linux servers, check if your system is running a vulnerable kernel version and apply the latest security updates. If patching is not possible right away, consider the workarounds: disable SYN cookies and use a single RX queue. Monitor your systems for unusual crashes or reboots, as these could be signs of attempted exploitation.
Why it matters
Linux powers much of the internet and many business systems. A remote crash vulnerability could disrupt websites, cloud services, and remote access. Even though attackers cannot steal data, downtime can cause real problems for organisations.
Key points
- NoisyTCP is an 11-year-old Linux kernel flaw that lets attackers crash servers.
- The bug affects systems running Nginx, Apache, or SSH with default settings.
- Attackers cannot steal data or run code, but can cause denial of service.
- A patch is available and should be applied as soon as possible.
- Workarounds exist for those who cannot patch immediately.
Sources
BleepingComputer
Reference

