Published Nov 16, 2026, 4:19 PM EST Tyler Cross is an author for How-To Geek who reports on a wide range of cybersecurity stories. Before this, he spent 5 years creating cybersecurity articles under the Kape brand, including both short- and long-form blog posts. He also has 2+ years of experience creating news articles, YouTube scripts, and product reviews for a wide range of VPNs, antivirus software, password managers, and more. Outside of work, I am an avid tabletop gamer and enjoy writing my own TTRPG systems and campaign modules. Sign in to your How-To Geek account Security researchers recently discovered an 11-year-dormant vulnerability within Linux's handling of TCP, which they nicknamed NoisyTCP (CVE-2026-99288). The bug allowed a remote, unauthorized attacker to crash vulnerable servers over the internet without needing to log in to their account first. It affects the operating system itself, so a single attacker could bring down an entire server, including the other services that rely on it. "In standard Red Hat Enterprise Linux deployments, TCP networking is universally enabled, making any system with active network listeners susceptible to high-volume socket recycling traffic," explain security researchers from Red Hat Enterprise. The bug has been active since October 3rd, 2015, when developers accidentally introduced it as part of an update that changed how Linux tracks incoming connections so processors could handle certain packets without waiting for a shared lock. The bug comes from a NULL pointer dereference weakness in the kernel TCP subsystems, meaning Linux is trying to use information that isn't there, causing a crash. Fortunately, the bug does not allow attackers to execute malicious code or arbitrary command execution. How NoisyTCP causes a crash Essentially, the vulnerability triggers when Linux systems find a connection record and remember its location. Something else would delete that information and take its place. When Linux later tries to use that connection record, it pulls up the new file, thinking it was the old one. However, Linux has not fully established the new record yet, so when it later tries to accept the connection and read it, the entire system crashes. "The socket caches involved use SLAB_TYPESAFE_BY_RCU, so memory can be reused before an RCU reader that retained its old address has finished. After a tuple match, __inet_lookup_established() and __inet6_lookup_established() acquire a reference and repeat the tuple check," the NIST explains. "They do not check whether the new object is hashed. If the address is reused for a socket with the same tuple, the lookup can acquire a reference to the new object and return it while its nulls node is unhashed. A PoC that drives reuse with a SYN cookie request socket reproduced the crash. The new request socket is unhashed and has a NULL rsk_listener. A lookup that had loaded the address of the old request socket acquired the reference published by tcp_get_cookie_sock() and returned the new object. tcp_v4_rcv() then read sk_state through the NULL listener." Researcher Hyunwoo Kim discovered the vulnerability and privately reported it to Linux. Linux took quick action to patch the vulnerability in the 6.12.117, 6.18.63, and 7.3.4 updates to the Linux Kernel. Computers running an older Linux Kernel remain vulnerable. The Linux kernel CVE team recommends that you update to the latest stable kernel version for this and many other bug fixes," said Greg Kroah-Hartman, the co-author of Linux Device Drivers, in an official security advisory for CVE-2026-99288. "Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all." If you aren't able to immediately update your computer, Kim advises that you disable SYN cookies or limit incoming packet processing to a single receive queue. Note that disabling your SYN cookies increases your vulnerability to SYN flooding attacks. Source: Bleeping Computer
Why one container running NoisyTCP can bring down an entire Linux system
Full Article
Original Source
Read the full article at Howtogeek →KhanList aggregates and links to publicly available news content. We do not host full articles from third-party sources. Always verify important information with original sources.