Vulnerabilities

CVE-2026-98432: critical Linux kernel flaw reachable through IPv4 TCP

A use-after-free race in IPv4 TCP connection handling can expose Linux servers to crashes, memory corruption and, under specific conditions, unauthenticated remote code execution. Anthropic's demonstrated exploit has not been released; patch availability depends on the distribution.

Conceptual illustration: CVE-2026-98432: critical Linux kernel flaw reachable through IPv4 TCP
Conceptual illustration · SecurCheck

What is confirmed

Published by the Linux kernel security team on 15 October 2026, CVE-2026-98432 affects IP-option handling during the establishment of IPv4 TCP connections. Vendors assign a CVSS v3.1 score of 9.8/10.

A race condition can cause use-after-free when concurrent code paths access connection-request IP options after release. Outcomes may include denial of service, memory disclosure or corruption; remote code execution is the most severe potential impact.

On 27 October, Anthropic reported developing and testing an exploit chain with Claude against a Linux server running an MPTCP listener. Its demonstration executed commands as root without credentials or user interaction.

On 2 November, Canonical said patches for Ubuntu 22.04 LTS, 24.04 LTS and 26.04 LTS were in the qualification-only -proposed pocket, while Ubuntu 26.10 already had a fixed kernel. Other vendors, including Red Hat, Debian and Amazon Linux, published their own advisories and patch schedules.

What it means

The flaw has existed in the Linux kernel since the 4.4 series. Exposure and fixed builds are distribution-specific: a lower kernel version number alone cannot prove vulnerability when a vendor has backported the fix.

The documented attack path involves IPv4 TCP packets carrying IP options during the network handshake, before application processing by services such as Apache, SSH or APIs. An exposed TCP service can therefore matter even when application software itself is fully patched.

MPTCP was used in the research exploit, but the underlying bug is not exclusive to MPTCP. Disabling that feature does not eliminate the flaw in ordinary IPv4 TCP processing.

Why this deserves high-priority attention

The risk sits in the kernel, reached before authentication on a host accepting inbound IPv4 TCP traffic. An attacker does not need an existing account, a web session or an application-layer bypass to reach this code path. Reliable root-level exploitation remains technically demanding and condition-dependent, but the published demonstration raises the priority of identifying exposed hosts.

Repeated attempts may target the race condition, and there may be few obvious application-level signs before a crash or memory corruption. Ordinary web application monitoring cannot guarantee detection.

Ubuntu: verify the patch actually running

As of 2 November 2026, Canonical listed a qualification-stage fix for Ubuntu 24.04 LTS in the 6.8.0-149.149 series and for Ubuntu 22.04 LTS in the 5.15.0-203.213 series. These are Ubuntu package versions, not generic Linux thresholds. Distribution advisories may change after publication and should be checked at deployment time.

Compare the running kernel (`uname -r`) with the kernel packages actually installed. A patched kernel package on disk does not protect a server that has not booted into it. Production fleets need a maintenance window, functional verification and a controlled reboot after the update.

nftables filtering: temporary exposure reduction, not a fix

Red Hat and France's CERT Santé describe dropping inbound IPv4 TCP packets carrying IP-header options (`ip protocol tcp ip hdrlength > 5`). This filters a traffic feature required by the described exploit path. It may, however, disrupt legitimate IPv4-option traffic, so operators must review their network requirements, existing firewall rules and reboot persistence.

Red Hat says this reduces exposure but cannot fully prevent exploitation, while Canonical recommends applying a patched kernel. Disabling MPTCP is likewise incomplete. The vendor's kernel update, installed and activated by a reboot, remains the definitive remediation.

What to do

Prioritise Linux hosts with reachable IPv4 TCP ports: web servers, SSH, VPNs, mail, accessible databases, edge devices and appliances. Record OS, kernel branch, running version and the vendor advisory for each host.

Install the vendor-approved fixed kernel and schedule a controlled reboot. Then verify the running kernel with `uname -r`; do not treat package installation alone as completed remediation.

If an approved fix is not yet available, assess temporary service exposure restrictions or the documented IPv4-option nftables filter with your network team. Test its effect on legitimate traffic, protect administrative access and monitor kernel faults.

Record installed versions and verification results, follow vendor updates and distinguish laboratory proof from observed attacks.

Check a suspicious sign

SecurCheck's external scan can flag visible website anomalies, but it cannot prove the kernel is unaffected or replace host inventory and Linux kernel updates.

Explore the related risks

Sources

  1. Linux kernel security team — annonce CVE du 15 octobre 2026
  2. Anthropic — démonstration RCE Linux du 27 octobre 2026
  3. Ubuntu — correctifs en qualification au 2 novembre 2026
  4. Red Hat — bulletin RHSB-2026-016, filtrage et limites
  5. AWS — bulletin de sécurité 2026-160-AWS
  6. CERT Santé — avis du 3 novembre 2026