NewsSecurityInfrastructure

CVE-2026-98432: Linux TCP Flaw Enables Remote Root Access

Ubuntu and RHEL have gone 25 days without patching a CVSS 9.8 Linux kernel flaw. On October 27, Anthropic announced an internal Claude model achieved remote root access on a vulnerable server in 53 minutes. If your production stack runs on Ubuntu LTS or Red Hat Enterprise Linux, you are exposed right now — and there is no patch release date from either vendor.

What CVE-2026-98432 Actually Does

The bug has lived in the Linux kernel since version 4.4 — January 2016, a decade of dormancy. It sits in tcp_v4_syn_recv_sock(), the function that completes TCP handshakes. When a SYN packet arrives carrying IPv4 options (Record Route or Timestamp), the kernel stores those options in ireq_opt and hands the pointer to the new child socket without copying the data. If a second SYN retransmission lands on a different CPU at exactly the right moment, the options memory gets freed while another thread is still reading it. Classic use-after-free. The result is readable and writable kernel memory.

A few facts that deserve more attention: IPv6 is completely unaffected because the kernel correctly copies options in the v6 path. Failed race attempts do not crash the server — attackers can retry indefinitely without triggering anything visible in logs. The upstream fix, a two-line change by Eric Dumazet converting kfree() to kfree_rcu(), shipped October 5 — ten days before the CVE was published. The full technical breakdown is on The Hacker News.

The Go 1.24 Problem Nobody Is Talking About

Here is the angle most coverage is burying: since Go 1.24, Go programs enable Multipath TCP (MPTCP) by default on all listening sockets on Linux systems that support it. MPTCP listeners are the attack surface against which Anthropic confirmed remote code execution. Every Go service running on an unpatched kernel with Go 1.24 or later is standing up an MPTCP listener — likely without the developer knowing.

Fix it now. Set this environment variable before your service starts:

GODEBUG=multipathtcp=0

Or add the following line to your go.mod for a build-time permanent fix:

godebug multipathtcp=0

The Go Security Team notes these are fragile mitigations — a single MPTCP listener anywhere in your deployment still leaves you exposed — but it is the best available action today while vendor patches are pending.

Who Has Patched and Who Has Not

Debian shipped fixes within 11 days of the upstream patch. Oracle, Amazon Linux (kernel6.12 and kernel6.18), and SUSE all have fixes available. The two distributions that power the majority of cloud production deployments — Ubuntu LTS and RHEL 8/9/10 — have neither released patches nor announced release dates as of October 31. Rocky Linux and AlmaLinux are waiting on RHEL upstream.

Red Hat’s initial severity score of 5.9 (Moderate) was wrong and has since been updated to 8.1 (Important). Scanning tools may still report the old score, causing some enterprise teams to deprioritize remediation. The kernel team’s score is 9.8. Trust the 9.8. Track your distribution’s patch status on the Ubuntu CVE tracker.

What To Do Right Now

Three steps, in order of priority:

1. Identify your exposure. Run uname -r to confirm your kernel version, then check for active MPTCP listeners:

ss -H -lMn

Output means you have active MPTCP listeners. Disable them and restart the affected services.

2. For Go services. Apply GODEBUG=multipathtcp=0 immediately. Restart services. Verify with ss -Mlnp to confirm no listeners remain.

3. Network-level block. This nftables rule drops TCP packets carrying IPv4 options at the network layer. Normal traffic does not carry IPv4 options, so false positive rates are minimal. Test in staging first:

nft add table ip cve_2026_98432
nft add chain ip cve_2026_98432 pre '{ type filter hook prerouting priority -300; }'
nft add rule ip cve_2026_98432 pre meta l4proto tcp ip hdrlength gt 5 counter drop

To undo: nft delete table ip cve_2026_98432. This is a stopgap. Apply the kernel patch the moment your distribution ships it. TuxCare has a full mitigation guide including rebootless patching options.

The Bigger Problem

CVE-2026-98432 follows the RegreSSHion script from 2024: a researcher demonstrates a working exploit, major distributions take weeks to ship patches, and enterprises get caught in the gap. The upstream kernel had a fix 26 days ago. Debian moved in 11 days. Ubuntu and Red Hat are still working on it.

This is not a wait-and-see vulnerability. No wild exploitation has been confirmed yet, but the exploit mechanism is now public knowledge and the race condition is forgiving enough to retry silently. Apply every available mitigation today. Watch the Ubuntu Security Notices (USN) and Red Hat Security Bulletin feeds. When patches arrive, apply them immediately and reboot. A patched kernel package that is not the running kernel is no protection at all.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

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

    More in:News