SOKK Advisories

Cloudflare Zero Wire

Linux IPv4 TCP use-after-free

Prioritize patching. Atlas updated its distribution review to report fixed RHEL kernels and remaining vendor-specific patch gaps. Install your distribution's fixed kernel and verify it is running after a reboot or vendor-supported activation. Updating containers alone does not patch the host.

  • Kernel
  • Memory corruption
  • MPTCP
  • Race condition
  • RCE

Prioritize patching · Last reviewed

A race condition in Linux's IPv4 TCP connection handling can expose kernel memory, crash a host, or allow remote code execution before application authentication.

Updates

  • : Atlas updated its distribution review to report fixed RHEL kernels and remaining vendor-specific patch gaps.
  • : Red Hat published a Critical-impact bulletin and interim network-filtering guidance.
  • : The Go Security Team published MPTCP applicability guidance, subsequently mirrored on oss-security.
  • : Anthropic disclosed a working research exploit for remote root command execution against MPTCP listeners.
  • : The Linux kernel CNA published the CVE record with upstream fix references.

Details

CVE-2026-98432 is a use-after-free in the Linux kernel's IPv4 TCP handshake. One operation can free stored IPv4 options while another CPU is still reading them to construct a connection reply. The flaw dates to Linux 4.4. The Linux kernel CNA rates it Critical, with a CVSS 3.1 score of 9.8.

The vulnerable processing happens before an application authenticates a connection. A remote peer can trigger a race that discloses kernel memory, corrupts memory, or crashes the host. Anthropic demonstrated root command execution on servers exposing a Multipath TCP (MPTCP) listener.

The Go Security Team warns that the underlying bug is not specific to MPTCP and that similar attacks may be possible without MPTCP listeners. Its guidance notes that Go programs enable MPTCP listeners by default on Linux from Go 1.24, subject to configuration. Disabling MPTCP is not a substitute for patching the kernel.

The upstream fix defers freeing the options until concurrent readers have finished. Distribution vendors backport the fix under their own package versions. Updating an application or rebuilding a container image alone does not patch the host kernel, and installing a new kernel does not by itself prove that the running kernel is fixed.

Risk

Researchers demonstrated root command execution against MPTCP listeners; other IPv4 TCP services may also be affected. Reports reviewed on November 2 did not confirm real-world attacks.

Affected deployments

Linux hosts with an affected kernel and IPv4 TCP networking, including container hosts and Kubernetes nodes. Prioritize reachable MPTCP listeners; other IPv4 TCP services may also be affected.

Recommended actions

Install your distribution's fixed kernel and verify it is running after a reboot or vendor-supported activation. Updating containers alone does not patch the host.

  1. Inventory running Linux kernels and reachable IPv4 TCP services, including container hosts, Kubernetes nodes, appliances, and managed infrastructure.

  2. Check the running kernel against your distribution or platform advisory, including any backported fixes.

  3. Install the fixed kernel, prioritizing Internet-facing hosts and MPTCP listeners. Reboot or use the vendor-supported activation procedure, then verify that the running kernel includes the fix.

  4. Where a patch cannot yet be applied, consult vendor mitigation guidance. Red Hat describes IPv4-option filtering as exposure reduction, not complete prevention; verify compatibility with your network and workloads.

Use this prompt with an agent that can inspect your infrastructure.

Assess whether the infrastructure available to you is affected by CVE-2026-98432, the Linux IPv4 TCP use-after-free vulnerability. Perform a read-only assessment within your authorized access. Do not send exploit packets, stress-test listeners, change firewall rules, or reboot systems.

1. Verify the current Linux CVE record at https://www.cve.org/CVERecord?id=CVE-2026-98432 and the relevant distribution or platform vendor advisories. Consult https://access.redhat.com/security/vulnerabilities/RHSB-2026-016 and the Go Security Team's applicability guidance at https://www.openwall.com/lists/oss-security/2026/10/30/1 where relevant. Establish affected and fixed builds, including vendor backports. Cite sources and retrieval dates; flag anything you cannot verify.

2. Inventory accessible Linux hosts, virtual machines, container hosts, Kubernetes nodes, appliances, and managed platforms. Record the asset, environment, owner where known, distribution, running kernel release/build, installed kernel packages, and any verified livepatch status. Use read-only evidence such as uname -r, uname -v, package metadata, and platform inventory. Match vendor fixes to the running kernel, not merely an installed update or an image tag. Containers share their host's kernel: rebuilding an application image does not patch it. If host access is unavailable, record that gap and request confirmation from the operator or provider.

3. Identify Internet-facing and internal IPv4 TCP listeners and the paths that can reach them, including direct-origin access, load balancers, and container networks. Check MPTCP listeners and configuration in relevant network namespaces using read-only inspection such as ss -Mlnp and sysctl net.mptcp.enabled where supported. Review Go services and their MPTCP settings. An enabled sysctl alone does not prove that an MPTCP listener exists; an empty result without sufficient access does not establish absence across the host. Prioritize exposed MPTCP listeners, but do not classify a kernel as unaffected simply because MPTCP is disabled or no such listener was found.

4. Assess network-layer compensating controls separately from kernel patch status. Where accessible, inspect filtering of IPv4 TCP packets carrying IP options and whether alternate or container-network paths bypass it. Do not confuse IPv4 options with TCP options or claim that filtering fully fixes the vulnerability. HTTP WAF rules do not address this pre-HTTP TCP-handshake flaw. A proxy or firewall configuration alone does not establish that every path to the host is protected.

Return a concise summary and a table: asset/host | running kernel/build | assessment (affected, fixed, not applicable, or unknown) | IPv4/MPTCP exposure | supporting evidence | next action. Separate kernel applicability from network reachability. Prioritize affected Internet-facing systems, identify installed-but-not-active fixes, and link to current vendor remediation and activation guidance. List unassessed systems and the exact evidence or access needed to resolve unknowns. Distinguish a demonstrated research exploit from exploitation in the wild; do not infer absence of compromise from patch status or a lack of alerts. Propose verification steps without applying changes, and limit conclusions to the scope actually assessed.

Find more information and resources at https://radar.cloudflare.com/zero-wire/linux-ipv4-tcp-use-after-free

Cloudflare coverage

Service status

Cloudflare was not impacted by this vulnerability.

Product coverage

Magic Transit customers can use Cloudflare Network Firewall to reduce exposure by filtering IPv4 TCP packets carrying IP options before they reach their infrastructure. Coverage depends on routing and firewall configuration and does not replace kernel patching.

Evidence and sources

CVE record

The Linux kernel CNA documents the race condition, upstream affected and fixed branches, and Critical CVSS 3.1 severity of 9.8. Distribution package versions must be checked against vendor advisories.

Vendor advisory

Red Hat describes unauthenticated remote code execution potential and broad IPv4 TCP exposure. Its interim filtering guidance reduces exposure but does not replace kernel updates.

Runtime applicability

The Go Security Team explains MPTCP listener defaults and warns that systems without MPTCP listeners may still be vulnerable to similar attacks.

Exploit evidence

Anthropic demonstrates root command execution on Linux servers with MPTCP listeners.

CISA KEV

CVE-2026-98432 was not present in the CISA KEV feed retrieved on 2 November 2026 (catalog version 2026.10.30). Absence from KEV is not evidence that exploitation cannot occur.

Product coverage

Magic Transit includes Cloudflare Network Firewall. Its IPv4 header-length field supports filtering packets carrying IP options; this is a configurable exposure-reduction capability, not a verified default-on CVE-specific mitigation.

Technical analysis and distribution tracking

Atlas provides a technical explanation and links to distribution patch trackers. Its 1 November update reports RHEL fixes and outstanding updates elsewhere; consult each vendor for current availability.

View details