CVE-2026-98432: Remote RCU Use-After-Free Vulnerability Patched in Linux IPv4 TCP Handshake
A CVSS 9.8 critical vulnerability in the Linux IPv4 TCP stack allows remote, unauthenticated attackers to trigger a use-after-free during request socket processing before application-layer execution. Upstream stable trees released fixes extending back to Linux 4.4, but downstream distribution coverage remains fragmented.
Mechanism and Root Cause
The flaw designated as CVE-2026-98432 stems from improper object lifetime management within the Linux kernel's IPv4 TCP stack during 3-way handshake execution. When processing incoming TCP request packets, the kernel stores IPv4 option data inside a request socket structure (`ireq_opt`) to mirror options back in subsequent handshake replies. During the allocation transition from a half-open request socket to a full socket structure, the kernel copied option pointers (`inet_opt`) without performing a deep copy of the underlying buffer.
If the connection is prematurely closed, the kernel frees the memory associated with these options immediately. A concurrent thread executing on a separate CPU core can attempt to read the freed memory location to construct a handshake response packet. The resulting race condition exposes hosts to remote kernel memory corruption, arbitrary code execution, or denial of service. The upstream patch authored by Eric Dumazet addresses the bug by enforcing an RCU grace period before freeing `inet_opt` and `ireq_opt` structures.
Exploitability and Attack Surface
The vulnerability triggers completely within kernel space during initial packet processing, bypassing application-level authentication entirely. Because a failed exploitation attempt typically results only in a dropped connection rather than an immediate kernel panic, attackers can repeatedly attempt to hit the race condition without rendering the target host offline.
Security researchers at Anthropic demonstrated a functional root exploit against systems running a Multipath TCP (MPTCP) socket listener. Applications compiled with Go are exposed to this vector by default, as the standard Go runtime enables MPTCP listeners automatically. However, the root cause resides in base IPv4 option handling rather than MPTCP, rendering non-MPTCP network listeners potentially vulnerable to alternative execution paths.
Distribution Patch Matrix and Remediation
Upstream stable branches released patches between October 11 and October 18, 2026. Fixed kernels include 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10, and 7.3. Downstream distribution patch status remains varied:
- Red Hat Enterprise Linux: Fixed kernels for RHEL 8.10, 9.8, and 10.2 shipped on November 1, 2026. OpenShift Container Platform and RHEL CoreOS remain unpatched.
- Ubuntu: All LTS and interim releases (16.04 through 26.10) remain vulnerable without published updates.
- Debian: Fixes are live in Debian 12 Bookworm (DLA-4841-1 / DLA-4850-1), Debian 13 Trixie, and unstable.
- Amazon Linux & Oracle UEK: All kernel families carry backported fixes.
- AlmaLinux: Patched kernels for EL 8, 9, and 10 remain in testing repositories.
Engineers unable to apply kernel updates immediately should drop IPv4 packets carrying IPv4 options via edge packet filters or host firewall rules, disable unused MPTCP interfaces, and prioritize host reboots for nodes serving Go application binaries.