CVE-2026-98432: pre-auth use-after-free in the Linux kernel TCP stack
A use-after-free in the IPv4 TCP path (CVSS 9.8) can give a remote attacker root. Affected kernels, the MPTCP myth, exposure checks and remediation.
The third of three critical RCE flaws this week — and the broadest, because the bug lives in the core TCP path rather than an optional module. See also the actively-exploited Apache Roller RCE, the Apache HTTP/2 race condition, and the 2026 RCE field guide.
Scope and ethics. Exposure detection and remediation only, for systems you own or are authorized to assess.
Description
A use-after-free in the IPv4 TCP stack. IP options stored with a pending connection’s request socket can be freed while another CPU still references them (ip_options_build()); the child socket takes ownership of those options without copying them in tcp_v4_syn_recv_sock(), and socket migration follows a similar path. IPv6 largely escapes the issue because the kernel copies IPv6 options. The defect dates back to kernel 4.4.
Impact
Remote, pre-authentication kernel memory corruption. The worst-case outcome is root-level code execution on the host. Because the vulnerable code is in the standard TCP handshake path, this is a broad exposure across servers, appliances and containers hosts — not a niche add-on.
Prerequisites (for the attack to work)
- Network reachability to a listening TCP service.
- A vulnerable kernel: anything from 4.4 up to the fixed stable releases listed below.
- MPTCP caveat — read this carefully: the public research exploit used an MPTCP listener, but Red Hat states MPTCP is not required, and nodes with MPTCP disabled remain affected. Do not treat “MPTCP off” as “safe.”
Steps to reproduce (exposure validation)
# 1) Running kernel — compare against your distro's fixed version AFTER a reboot
uname -r
# 2) Is MPTCP enabled? (reduces, but does NOT eliminate, the surface)
sysctl net.mptcp.enabled 2>/dev/null
# 3) RHEL / derivatives: installed vs. running kernel
rpm -q kernel; echo "running: $(uname -r)"
# 4) Debian / Ubuntu: installed kernel images
dpkg -l 'linux-image*' | awk '/^ii/{print $2, $3}'
Compare the running kernel to your vendor’s fixed build. Exploit research is linked below for lab use against a kernel you control.
Remediation
- Patch the kernel and reboot. Upstream fixes 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; the kernel CVE team recommends moving to the latest stable rather than cherry-picking the patch. Distro fixes: Red Hat RHSA-2026:93412 / 93413 / 93414 (RHEL 8/9/10), Ubuntu 7.3.0-10.10 on 26.10 (others in
-proposed), and patched Amazon Linux streams. - Mitigations until you can reboot — not a fix:
sysctl -w net.mptcp.enabled=0(andGODEBUG=multipathtcp=0for Go 1.24+ services), then restart affected services.- Drop inbound IPv4 packets carrying IP options (AWS publishes an iptables rule for this).
- Front the host with a separate load balancer or managed service that terminates TCP — a proxy on the same host does not count.
- Watch for the reported scanning: researchers noted probing of port 443 over MPTCP that may be hunting for this bug.
References
- Red Hat — CVE-2026-98432 · RHSB-2026-016
- Ubuntu — CVE-2026-98432
- Upstream fix commit — git.kernel.org
- AWS security bulletin
- The Hacker News write-up
Verify every version against the vendor advisory before acting. Published 16 Nov 2026.