Linux kernel · CVE-2026-98432
Linux TCP root
Patch now if…Any IPv4 TCP server. Root shown only via MPTCP.
A race in the kernel's IPv4 TCP handshake code lets a remote attacker with no login corrupt kernel memory by sending connection requests that carry IP options. On 27 Oct, Anthropic showed remote root against a server with a Multipath TCP (MPTCP) listener, but the bug is in plain TCP, so turning off MPTCP doesn't make you safe. Full exploit code isn't public and no attacks are reported.
How scary is it?
Are you affected? only if all are true
1Kernel 4.4 or later, not yet patchedcommand
Upstream fixes: 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, 7.3. Distro kernels backport, so compare with your distro's fixed version under Update. RHEL 6 and 7 are not affected.1,4,10
uname -r2Accepts IPv4 TCP connectionscommand
Any IPv4 TCP listener counts, MPTCP or not: Red Hat says MPTCP is not required, and RHEL with MPTCP off by default is still affected. IPv6 is not affected by the main bug. Nearly every server has a TCP listener.1,4,5
sudo ss -tlnpWhat to do
1Update the kernel and reboot
Install your distro's fixed kernel (listed below), then reboot. Ubuntu 20.04 (5.4.0-247.267) and 18.04 (4.15.0-263.275) fixes are in Ubuntu Pro only. Debian 12's linux-6.12: 6.12.113-1~deb12u1. Cloud and HWE kernels have their own versions.8,9,10,14
Latest safe versions checked 20 Nov
2Can't reboot yet? Live patch or filtercommand
RHEL 8, RHEL 9.8 EUS and some RHEL SAP streams have a kpatch live patch (19 Nov; plain RHEL 9 has none) that avoids the reboot. Otherwise drop inbound IPv4 TCP packets with IP options in an nftables input chain (normal TCP options are fine). That reduces exposure but isn't a fix: traffic between containers on the same host can skip it.10,4,9,11
ip protocol tcp ip hdrlength > 5 counter drop3Optional: turn off MPTCPcommand
Blocks the known root path only (the public demo used an MPTCP listener; Go 1.24+ programs open them by default). May break programs that need MPTCP. For Go services, GODEBUG=multipathtcp=0 does the same per program. sudo ss -Mlnp lists MPTCP listeners.2,3,6,7
sysctl -w net.mptcp.enabled=0This page shows you how to check. It can't tell you you're safe.
Sources (17) and changelog
- CVE record (kernel CNA): bug, 9.8, fixed versions 15 Oct
- Anthropic: remote root demo on MPTCP listener 27 Oct
- Go team (oss-security): Go 1.24+ MPTCP default 29 Oct
- Red Hat RHSB-2026-016: MPTCP not required, nft rule 11 Nov
- BleepingComputer: early ratings, no attacks 30 Oct
- oss-security: sysctl to disable MPTCP 30 Oct
- CIQ (oss-security): MPTCP-off not enough 2 Nov
- Debian tracker: fixed versions
- Ubuntu: fixed versions, firewall stopgap 18 Nov
- Red Hat: CVE page, RHEL errata
- oss-security: filter bypass between containers 31 Oct
- CISA KEV catalog: not listed
- Phoenix Security: trigger code public, no full chain
- Ubuntu USN-9170-1: 20.04 and 18.04 fixed (Ubuntu Pro) 19 Nov
- Launchpad: Ubuntu kernel builds
- Debian tracker: linux package versions
- Red Hat: kernel errata (CSAF)
- Ubuntu 20.04 and 18.04 fixed through Ubuntu Pro. RHEL 10.3 fixed. kpatch coverage clarified. Safe versions added.
- Review: verdict set to Patch now if… (no public exploit or attacks), kpatch, correct listener check.
- RHEL 8, 9 and 10 fixed kernels released.
- Red Hat: MPTCP is not required to hit the bug.
- Anthropic shows remote root on an MPTCP server.
- Published.