CVE-2026-98432 - critical Linux kernel bug (CVSS 9.8)

Derek Ross posted about it this X.com, copying the body text below.

Looks like PureOS Crimson is already patched.

  • :police_car_light: 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:

    1. 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.

    2. If your distro has a fix, update and reboot.

    3. 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.

    4. 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.

    5. 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. :shield:
    get root shell" risk.

Are any versions of 6.8.X affected or safe?

$ sudo sysctl -w net.mptcp.enabled=0
sysctl: cannot stat /proc/sys/net/mptcp/enabled: No such file or directory

What is best practice in above case, do you know?

Thanks again for you time

Linux 6.8 is unsupported since May 2024.

Hmm, thanks. I have a cloud provider that is either trolling or using a different versioning scheme.

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.

What about 6.18.0.1-librem5, is that one potentially fixed independently of the version numbers provided?

The version currently available in crimson, as seen in the package version and as reported by uname -a, is 6.18.56pureos1~cri1.

Thank you @dos you are right, and I am wrong, and if I understand correctly then my L5 is safe:

purism@pureos:~$ uname -r
6.18.0-1-librem5
purism@pureos:~$ uname -a
Linux pureos 6.18.0-1-librem5 #2 SMP PREEMPT 6.18.56pureos1~cri1 2026-10-12 00:01:41 UTC aarch64 GNU/Linux
purism@pureos:~$ 

i thought i had upgraded completely to crimson, but i see this:

$ uname -a Linux myhostnamee 6.1.0-53-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.187-1 (2026-09-07) x86_64 GNU/Linux

cat /etc/os-release says this:

ID=pureos
NAME=PureOS
PRETTY_NAME=“PureOS 11 (Crimson)”

VERSION_ID=“11”
VERSION_CODENAME=crimson

HOME_URL=“https://pureos.net/”
SUPPORT_URL=“FAQ – Purism”
BUG_REPORT_URL=“https://tracker.pureos.net/”

LOGO=pureos-logo-icon

did i miss a step of the upgrade?

sudo aptitude update and sudo aptitude full-upgrade do nothing at the moment, so i should be all caught up but it seems i am not.

any suggestions?

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.

And for completeness, I suspect that 7.0.0-42 is vulnerable (the version that comes with Ubuntu 26.04 LTS) and 7.0.0-43 may be needed.

Info relating to Ubuntu: CVE-2026-98432 | Ubuntu

Official description of CVE: https://www.cve.org/CVERecord?id=CVE-2026-98432

Seems like his keyboard’s Enter key is broken. :frowning:

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.