Check a Linux server for CVE-2026-98432 (IPv4 TCP use-after-free, CVSS 9.8): root cause explained, read-only check script and mitigations.
Understand and check CVE-2026-98432, the race in the Linux kernel's IPv4 TCP handshake that lets a remote attacker use freed kernel memory. Anthropic's Frontier Red Team turned it into a zero-click root exploit against servers with a multipath TCP (MPTCP) listener. As of October 30, 2026, Ubuntu and Red Hat have no fixed kernel yet.
Paste the command output in the browser instead: https://fbuff.com/tools/cve-2026-98432-checker/ (runs locally, nothing is uploaded)
Every TCP connection starts with a handshake: the client sends SYN, the server answers SYN-ACK, the client replies ACK. Between SYN and ACK the kernel keeps a small placeholder for the half-open connection, a request socket. If the client's SYN carried IPv4 options (Record Route, Timestamp and the like), the kernel keeps them with the placeholder (ireq_opt), because the SYN-ACK has to echo them back.
When the ACK arrives, tcp_v4_syn_recv_sock() turns the placeholder into a full socket and hands it the same options block instead of a copy. Two objects now point at one block of memory. When the full socket is destroyed, inet_sock_destruct() frees that block at once with a plain kfree().
The placeholder sits in the established-connections hash table, which other CPUs read without a lock (that design came with commit 079096f103fa, "tcp/dccp: install syn_recv requests into ehash table", Linux 4.4, 2015). If the client retransmits its SYN at the right moment, another CPU is resending the SYN-ACK and reads the options in ip_options_build() while the block is being freed: a use-after-free.
Think of a coat check that gives the same ticket to two people. When one leaves, the attendant throws the ticket away while the other is still walking to the counter with it.
The fix (upstream commit e3f33b0a1d89, "ipv4: free inet_opt and ireq_opt after an RCU grace period", 7.3-rc7) frees the block with kfree_rcu(), which waits until every CPU has finished reading. IPv6 is not affected by the main issue because tcp_v6_syn_recv_sock() copies the options. A second path to the same memory exists through request migration (net.ipv4.tcp_migrate_req=1 or a BPF_SK_REUSEPORT_SELECT_OR_MIGRATE program).
| Scorer | Score | Note |
|---|---|---|
| Linux kernel CVE team (CNA) | 9.8 | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Red Hat | 8.1 | AC:H: the race is hard to win (preliminary) |
| Ubuntu | 9.8, priority High |
MPTCP lets one connection use several paths at once. On Linux it is opt-in: a program must ask for an MPTCP socket, and ss -Mltn lists the ones listening. Anthropic's exploit targets "Linux servers with a multipath TCP listener". Neither the CVE record nor the fix mentions MPTCP, and Anthropic has not said whether servers without one can be taken over. An MPTCP listener is the proven path to root; every unpatched server still runs the faulty code.
| Distribution | Status |
|---|---|
| Debian 12 bookworm | Fixed: linux 6.1.190-1 (DLA-4841-1), linux-6.12 6.12.113-1~deb12u1 |
| Debian 13 trixie | Fixed: linux 6.12.113-1 (DSA-6568-1) |
| Ubuntu 22.04, 24.04, 26.04, 26.10 | Vulnerable, fix in progress |
| Ubuntu 16.04, 18.04, 20.04 | Vulnerable |
| Ubuntu 14.04 | Not affected |
| Red Hat Enterprise Linux | Affected; Red Hat says no mitigation meets its criteria |
| Upstream stable | Fixed in 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3 |
curl -fsSLO https://raw.githubusercontent.com/fbuff-tools/cve-2026-98432-checker/main/check.sh
sh check.sh
The script reads uname -r, /etc/os-release, the kernel package changelog (rpm -q --changelog, or apt changelog, which needs network), sysctl net.mptcp.enabled net.ipv4.tcp_migrate_req and ss -Mltn. It prints a verdict and exits with 0 (patched or not affected), 1 (vulnerable) or 2 (could not tell). It only reads; nothing is sent or changed. Run it on the host: containers share the host kernel.
Distribution kernels such as Ubuntu's 6.8.0-85 or RHEL's 5.14.0-570 backport fixes without changing the version number, so only their changelog can tell. Upstream-style versions (6.12.113+deb13) are compared with the fixed releases above.
sudo apt update && sudo apt full-upgrade # Debian, Ubuntu
sudo dnf upgrade kernel # RHEL family, Amazon Linux 2023
sudo zypper patch # SUSE
sudo reboot
sudo sysctl -w net.mptcp.enabled=0
sudo sysctl -w net.ipv4.tcp_migrate_req=0
printf 'net.mptcp.enabled = 0\nnet.ipv4.tcp_migrate_req = 0\n' | sudo tee /etc/sysctl.d/90-cve-2026-98432.conf
ip_options_build or ip_build_and_send_pkt (journalctl -k), or bursts of SYNs with IPv4 options from one source.None of steps 2-4 replace the patch, and no vendor has confirmed them as a full workaround.
Related: KSMBD checker, HTTP2Shell checker, PHP2Shell checker.
Information as of October 30, 2026; fix status changes quickly, so check your vendor's tracker. MIT license. Made by fbuff.