An Anthropic AI just demonstrated a working remote root exploit against a Linux kernel bug — and if you’re running Ubuntu or RHEL, there is still no patch available. CVE-2026-98432 is a use-after-free in the kernel’s IPv4 TCP stack, rated 9.8 critical by the Linux kernel security team. The exploit requires no credentials, no user interaction, and no local access. It hits you over the network.
What the Flaw Actually Is
The bug lives in tcp_v4_syn_recv_sock, the function that creates a child socket when a TCP handshake completes. The function transfers an options structure called ireq_opt to the new socket without copying it. If a second CPU simultaneously processes a retransmitted SYN for the same connection, it accesses that same options structure while the first CPU is freeing it. The result is a classic use-after-free: one thread reads memory after another has reclaimed it.
To trigger it, an attacker sends SYN packets with IPv4 Record Route or Timestamp options set, then retransmits the SYN to win the race. The target needs to have a multipath TCP (MPTCP) listener running.
Check Your Distro Right Now
Most major distributions have shipped fixes. Ubuntu and RHEL have not.
| Distribution | Status |
|---|---|
| Debian 12 / 13 | Fixed (DSA-6568-1 / DLA-4841-1) |
| Amazon Linux 2023 | Fixed (Oct 24–29) |
| SUSE / openSUSE | Fixed |
| Oracle Linux | Fixed |
| Ubuntu 22.04–26.10 LTS | NOT FIXED |
| RHEL (all versions) | NOT FIXED |
Run uname -r and compare against the fixed upstream versions: 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, and 7.3.x. If you’re on Debian or Amazon Linux and have updated recently, you’re likely patched. If you’re on Ubuntu or RHEL, you’re not — regardless of how recently you ran apt upgrade or dnf update.
The CVSS Score Argument — And Why It Matters to You
Here’s where it gets interesting. The Linux kernel team rates CVE-2026-98432 at 9.8 — critical. Red Hat rates it 5.9 moderate, arguing that winning the race condition is difficult and that only a denial-of-service crash has been demonstrated in practice, not code execution.
Then Anthropic published its research. An unreleased Claude model built a full remote root exploit chain: first leaking a kernel address to bypass KASLR (48 minutes), then redirecting execution to attacker-controlled code (5 more minutes). No user interaction. No authentication. Root shell delivered over the network.
If your security team triages by vendor CVSS — and most enterprise teams do — this bug may not be sitting in your emergency patch queue. It should be. The Red Hat score assumes human attacker capability. The Anthropic demonstration uses AI. That distinction is now operationally meaningless.
Temporary Mitigation While You Wait
The upstream fix is in the kernel tree. Your distro just hasn’t shipped it yet. While you wait, you can reduce the attack surface:
# Disable TCP request socket migration
sysctl -w net.ipv4.tcp_migrate_req=0
# Disable MPTCP if not in use
sysctl -w net.mptcp.enabled=0
Caveats: Red Hat explicitly says no mitigation meets its standards for stability. And MPTCP is opt-in on Linux — standard applications don’t use it unless they ask for it explicitly. If you’re not running anything that calls MPTCP sockets, your exposure is lower. But “lower” is not “zero” — the race condition can still be triggered through standard IPv4 TCP options without MPTCP enabled.
What This Tells You About Patching in 2026
The kernel team pushed the fix upstream. Debian and Amazon Linux absorbed it and shipped within days. Ubuntu and RHEL, with their more conservative patch validation cycles, are still working on it two weeks later. That gap — between “fix exists in the wild” and “your distro ships it” — is exactly the window that an AI-powered attacker exploits.
Anthropic’s exploit took 53 minutes to build from a standing start. Traditional race condition exploits take days to develop for even skilled researchers. AI collapses that window. The patching cycle hasn’t. The Cloud Security Alliance documented this collapse in detail — the mean time from public CVE to weaponized exploit has dropped from weeks to hours in 2026.
What to Do
- Run
uname -ron every Linux server and compare to fixed versions listed above. - If on Ubuntu or RHEL, apply the sysctl mitigations as a stopgap.
- Watch Ubuntu’s CVE tracker and Red Hat’s advisory page for patch availability.
- Check whether your managed cloud provider has pushed a kernel update out-of-band — cloud providers often move faster than distro vendors on critical issues.
- Stop using vendor CVSS scores as your only triage signal. Follow upstream kernel CVE team scores instead.

