NoisyTCP (CVE-2026-99288): how to update Debian 12 and 13

A Linux kernel that panics because someone sends it TCP packets. No password, no access, from the other side of the network. This is the NoisyTCP vulnerability, CVE-2026-99288, and it affects almost every distribution.

Server under a burst of network packets: the NoisyTCP vulnerability throws the kernel into a panic

I’ll sum up what you need to know for Debian 12 and 13. The sources are the Debian Security Tracker entry and the advisory from the researcher who found it.

What it is, in short

It’s a race condition in the kernel, in the lookup of already established TCP sockets. Two receive queues process packets at the same moment. In one particular case, tied to SYN cookies, the kernel gets hold of an object without its listener. Then it reads it. The result: a NULL pointer dereference and a kernel panic.

The flaw has been in the code since 3 October 2015. The upstream fix is dated 3 November 2026. That’s about eleven years of latent vulnerability.

No unusual configuration is needed. A listening service is enough: Nginx, Apache, SSH, a proxy.

Who is exposed to the NoisyTCP vulnerability

It takes a server that spreads traffic across multiple CPUs. That happens in two cases:

  1. The network card has at least two receive queues (RX queues).
  2. RPS (Receive Packet Steering) is enabled.

Timing depends heavily on the machine. According to the author, on VMs (QEMU/KVM) running Nginx, Apache or SSH with default settings, the panic comes after about 5 seconds to 2 minutes. On a quiet physical server, with 8 queues and an exploit tuned to the environment, it took about 14 hours.

So physical servers are harder to hit, but not immune. And VMs are the worst case.

The container case

This is where the real damage lies. A container uses the host’s kernel. If the attack hits the web server inside a container, it’s not just the container that goes down: the whole host goes down, and everything on it.

RCE risk: what we know and what we don’t

The confirmed impact is a remote denial of service. Remote code execution: the author writes “not yet, and basically, no”. They have a very limited exploit, lab-only and VM-only, and are still researching a general-purpose exploit.

However, there is a second path through the same flaw that can lead to a remote use-after-free. It is very hard to trigger. Keep an eye on it; don’t underestimate it.

Fixed versions

For the NoisyTCP vulnerability, the Security Tracker lists these fixed versions:

  • Debian 12 (Bookworm): from 6.1.192-1 (DLA-4906-1). The security repository now has 6.1.192-2.
  • Debian 13 (Trixie): from 6.12.117-1 (DSA-6628-1).

The linux packages in Bookworm and Trixie without the security repository are still listed as vulnerable. Check that the security repository is enabled.

How to update

sudo apt update
sudo apt upgrade -y
sudo reboot

The reboot is mandatory. Until you restart, the old kernel is still running.

Install just the new kernel (Debian 12 only)

This is the quick route, valid only for Debian 12. Install the fixed kernel directly, without upgrading the rest of the system. The 6.1.0-56 package corresponds to version 6.1.192-2, so it already includes the fix.

ARCH=$(dpkg --print-architecture)
sudo apt update
sudo apt install "linux-image-6.1.0-56-${ARCH}"

Here too you need a reboot: the new kernel only starts after sudo reboot. Then run the check below again. On Debian 13 this command does not apply: the package name is different, and for Trixie the full upgrade remains the valid route.

Keep the previous kernel at hand in the boot menu: I covered the risks of a kernel update in the article on the Debian kernel package 6.1.0-55, ext4 oops and rollback. For another TCP flaw from the same period, see the Linux kernel vulnerability in TCP IPv4.

How to check that you are protected

uname -r is not enough, because Debian applies fixes to the kernel without changing the main version number. What matters is the package version of the running kernel. This check reads it and compares it with the first fixed version:

v=$(dpkg-query -W -f='${Version}' "linux-image-$(uname -r)")
. /etc/os-release
case "$VERSION_ID" in 12) min=6.1.192-1 ;; 13) min=6.12.117-1 ;; esac
dpkg --compare-versions "$v" ge "$min" && echo "OK: kernel $v" || echo "VULNERABLE: kernel $v"

If it prints OK, the running kernel contains the fix. If it prints VULNERABLE, update and reboot, then run the check again. It also works before the reboot: it looks at the kernel running now, not the one you have just installed.

For a quick manual check there is uname -v, which on Debian shows the package version (for example Debian 6.1.192-1).

Two limitations. On Debian 12 with a kernel from bookworm-backports (6.12 series), the comparison would return OK even without the fix, because 6.12 is a higher number than 6.1.192: there you need to check the fixed backports version on the Security Tracker. And the check does not cover Debian 11 or other versions.

If you can’t reboot right away

There are two temporary mitigations, and both come at a price.

1. Disable SYN cookies. This closes the path the attack uses, but weakens the defence against SYN floods.

sudo sysctl -w net.ipv4.tcp_syncookies=0

The setting applies per network namespace: with containers, you have to apply it in each container that uses its own namespace.

2. A single receive queue and no RPS/RFS. This removes any chance of two contexts running at the same time. The cost: all network traffic goes through one CPU, which can become the bottleneck. You do it with ethtool on the card’s channels and by zeroing RPS/RFS on the interface.

These are stopgaps. The solution is an updated kernel and a reboot.

In short

The NoisyTCP vulnerability does not open the door to data thieves, but it can take down a server, or an entire container host, from the outside. If you run Debian 12 or 13: update, reboot, check the kernel version.

The commands are provided for information only. Try them in a test environment first and use them on your servers at your own risk: I accept no liability for service interruptions. Linux, Debian, Nginx, Apache, Docker and Kubernetes are trademarks of their respective owners.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

WordPress Cookie Notice by Real Cookie Banner