Decade-Old Linux Kernel Flaw 'NoisyTCP' Can Crash Nginx, Apache, SSH Servers
Researchers have disclosed a Linux kernel vulnerability, dubbed NoisyTCP, that has reportedly existed undetected for roughly 11 years. According to BleepingComputer, the flaw affects almost all Linux distributions and can be exploited to crash systems running common server software including Nginx, Apache, and SSH, even when those services are left in their default configuration.
The long shelf life of this bug underscores a recurring problem in open-source infrastructure: foundational components like the Linux kernel's networking stack are used so broadly, and have been audited so many times, that subtle flaws can persist for years without being caught. Vulnerabilities in the kernel's TCP handling are particularly concerning because they sit beneath almost every application-layer service, meaning a single flaw can have an outsized blast radius across web servers, remote access tools, and other network-facing daemons that most organizations rely on.
A denial-of-service condition at the kernel level is especially disruptive compared to application-specific bugs because it can take down multiple unrelated services on the same host simultaneously, and because kernel-level fixes typically require a system reboot to fully apply, unlike many application patches that can be hot-reloaded. Attackers favor this class of vulnerability precisely because it offers a low-complexity way to cause outsized operational impact, often without needing authenticated access.
Organizations running Linux-based infrastructure should prioritize identifying whether their kernel versions are affected and apply vendor-supplied patches as soon as they become available, following up with scheduled reboots where kernel updates require them. In the interim, network-level mitigations such as rate-limiting suspicious traffic patterns, segmenting exposed servers, and monitoring for abnormal connection behavior can reduce exposure. Given the breadth of distributions potentially affected, treating kernel patch management as a continuous, auditable process rather than an occasional task is advisable for any environment exposing Nginx, Apache, or SSH services to untrusted networks.
Source: BleepingComputer
Read the original report ↗This is an original summary written by CyberSkii for reference. All rights to the underlying reporting remain with the publisher linked above.