Linux Kernel TCP Flaw CVE-2026-98432: Red Hat and AlmaLinux Now Patched, Ubuntu Still Pending
A use-after-free in the Linux kernel's IPv4 TCP handshake, scored 9.8. Red Hat shipped RHEL 8, 9 and 10 fixes on 1 November; Ubuntu kernels are still pending. Status by distribution.
A use-after-free in the Linux kernel's IPv4 TCP handshake code, CVE-2026-98432, can be set off by an unauthenticated peer sending crafted SYN packets, and the CVE record carries a 9.8 critical score. Stable kernels with the fix were released on 15 October. Red Hat followed on 1 November with fixed kernels for RHEL 8, 9 and 10, but Ubuntu's are still pending. The flaw isn't in CISA's Known Exploited Vulnerabilities catalogue.
Why it's in the news now
On 27 October Anthropic's red team wrote that an unreleased Claude model built an exploit letting an attacker "send packets to Linux servers with a multipath TCP listener to run arbitrary commands as root", taking 48 minutes to leak a kernel pointer. The post names this flaw: "This vulnerability (CVE-2026-98432) was patched upstream". Its root exploit needs a multipath TCP listener; the bug itself sits in the ordinary IPv4 handshake. The kernel fix, written by Google's Eric Dumazet, credits an Anthropic researcher as the reporter.
The bug
An attacker sends a SYN carrying the IPv4 Record Route or Timestamp option, then races a retransmitted SYN against the connection being set up and torn down. The kernel frees the IP options while another CPU is still building a SYN-ACK from them, which leads to a use-after-free in ip_options_build(). The flaw dates back to Linux 4.4.
The score is disputed
Red Hat now rates it Critical at 9.8, and its wording is that it lets an unauthenticated remote attacker "cause kernel memory corruption or an immediate system crash". SUSE, Amazon and Oracle still score it 8.1, rating the attack complexity high.
What to install
The kernel CVE team lists the fix in upstream 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.56, 7.2.10 and 7.3. Distribution packages on 2 November:
- Red Hat: RHEL 8 kernel-4.18.0-553.182.1.el8_10 (RHSA-2026:93414), RHEL 9 kernel-5.14.0-687.64.1.el9_8 (RHSA-2026:93412), RHEL 10 kernel-6.12.0-211.72.1.el10_2 (RHSA-2026:93413), and RHEL 8 kernel-rt in RHSA-2026:93415. OpenShift's RHEL CoreOS images are still listed as affected. RHEL 6 and 7 aren't affected.
- AlmaLinux: the same kernel versions are in the production repositories for AlmaLinux 8, 9 and 10 since 2 November.
- Rocky Linux: no advisory yet.
- Oracle Linux: Unbreakable Enterprise Kernel updates ELSA-2026-500397, 500398 and 500399 since 16 October; the standard kernel for OL8 and OL10 in ELSA-2026-93414 and 93413 on 2 November. No OL9 standard-kernel erratum yet.
- Debian: trixie 6.12.113-1 (DSA-6568-1); bookworm 6.1.190-1 (DLA-4841-1).
- SUSE: SLE 16.0 and openSUSE Leap 16.0 have kernel-default 6.12.0-160000.40.1, and SLES 15 SP4, SP5 and SP6 LTSS kernels shipped on 29 October. SLES 15 SP7's kernel is still in QA, with live patches out.
- Amazon Linux: fixed in ALAS2023-2026-3365 for the default AL2023 kernel, and in ALAS2-2026-4065 for Amazon Linux 2.
- Ubuntu: builds for 26.10, 26.04, 24.04 and 22.04 are pending, none yet for 20.04 and older, and no security notice issued.
Until the kernel is updated
Turning off multipath TCP with net.mptcp.enabled=0 isn't enough: AlmaLinux notes it "only stops new MPTCP sockets from being created", and the bug sits in plain IPv4 TCP. Red Hat's bulletin gives an nftables rule that drops IPv4 TCP packets carrying options (ip hdrlength > 5), which AlmaLinux warns can miss traffic between containers on the same host and doesn't survive a reboot.
A kernel update takes effect after a reboot, unless it arrives as a live patch.


