PSA for anyone running a Linux server, node, or relay
CVE-2026-98432 is a critical Linux kernel bug (CVSS 9.8). Someone on the internet can send crafted TCP packets and take over your machine. No login needed.
Ubuntu and Red Hat haven’t shipped a fixed kernel yet. Debian, SUSE, Oracle and Amazon have.
What to do today:
Check your kernel: uname -r
Fixed versions: 6.1.190+, 6.6.159+, 6.12.113+, 6.18.56+, 7.2.10+ or 7.3+. Below that, you’re exposed.
If your distro has a fix, update and reboot.
If not, block the attack. It needs TCP packets with “IP options,” which normal traffic never uses. One nftables rule drops them. Log what gets dropped so you can see if someone’s probing you.
Turn off MPTCP unless you need it:
sysctl -w net.mptcp.enabled=0
Programs built with Go 1.24+ use MPTCP automatically, and that’s how the known exploit gets in.
Make it survive a reboot, and check it still works after one.
If you run a Bitcoin node, a Lightning node or a Nostr relay, your machine is on the internet by design. Do this today.
Self-hosting is freedom. Patching is part of the job.
get root shell" risk.
I’d guess that you’re running an older Ubuntu LTS release where Canonical is supporting that kernel entirely on their own, so you need to check whether Ubuntu has fixed this in their kernel and in which version if so.
Only the Librem 5 uses the 6.18 kernel on crimson. Other devices use the kernel from Debian Bookworm, which currently means 6.1.190-1 (there is also 6.12.113-1~deb12u1 available, but it’s not installed by default and you shouldn’t install it unless you know what you’re doing).
What is your cat /etc/apt/sources.list output? Maybe you have some oddity with the configured sources you get your updates from? Although I’m away from my x86 crimson at the moment, so just comparing to the Librem 5 setup at the moment.
Note the additional TCP option that can cause a similar problem, apparently. So only disabling MPTCP (Multipath TCP) may not be an adequate workaround (but the other option is off by default for me, it would seem).
Take care of this TCP/IP Bug. It is fixed in Linux above 6.12.113, 6.18.56, 7.2.10 and 7.3-rc7, but i do not like it. Because we have many smart home devices here with unknown running kernel or Linux firmware.
Edit: Thank you for moving it irvinewade. Did not found this thread before but did not searched for it too.