External risk intelligence

Linux Kernel MPTCP Subflow Vulnerability Allows Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-99634

This vulnerability exists within the Linux kernel MPTCP implementation related to subflow handling. While the kernel is network-reachable, this specific issue occurs during the complex MP_JOIN handshake process rather than via a common public-facing application, service, or management interface, making public internet exploitation uncommon and dependent on specific, less common network configurations.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A recent security advisory highlights a vulnerability in the Linux kernel's Multipath TCP (MPTCP) implementation. The issue stems from an incorrect handling of a feature called "Fast Open" during the MP_JOIN process, which could lead to a system crash or potential data exposure if exploited. The main concern is confirming relevance and exposure within affected systems.

  • MPTCP subflows incorrectly handled Fast Open.
  • Leadership should remember potential system instability.
  • Confirm relevance and any exposure within your environment.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted network request. This request would target the Multipath TCP (MPTCP) implementation within the Linux kernel. If the system is configured to use a feature called "Fast Open" on specific sub-connections (MP_JOIN subflows), the kernel may incorrectly handle a freed memory object, potentially leading to a system crash or other severe consequences.

  • Network access to a vulnerable system is required.
  • A malformed MP_JOIN request triggers the issue.
  • Potential for denial of service or code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could affect the Linux kernel's Multipath TCP (MPTCP) implementation when handling MP_JOIN requests. Specifically, it may allow a freed child socket to be exposed under certain conditions, potentially impacting network service behavior.

  • Kernel memory integrity could be impacted.
  • Exposure may occur during MP_JOIN subflow creation.
  • Service instability or data corruption could result.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Linux kernel's MPTCP implementation requires careful assessment by teams responsible for kernel management and network services. The initial step is to inventory all systems running the affected kernel version, determine their exposure to network threats, and identify the specific subflows that might be impacted. Subsequently, coordination between infrastructure and platform teams is necessary to plan and execute the remediation.

  • Kernel and infrastructure teams own remediation.
  • Verify MPTCP subflow configurations and reachability.
  • Plan and deploy kernel updates during maintenance.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is MPTCP in the Linux kernel?

MPTCP, or Multipath TCP, is a kernel-level networking feature that allows a single data connection to use multiple network paths simultaneously, such as switching between Wi-Fi and cellular data without dropping the session. This vulnerability specifically affects how the kernel manages 'subflows'—the individual network paths established when adding connections via the MP_JOIN process.

How does CVE-2026-99634 compromise kernel memory?

This is a memory management flaw where the kernel mishandles a network connection request. When a specially formed packet attempts to use a feature called 'Fast Open' during an MP_JOIN handshake, the system incorrectly maintains a reference to a memory object that should have been discarded. This creates a state where the kernel may process or expose data from an improperly freed socket.

Does any network traffic trigger this bug?

No. The vulnerability is not triggered by standard network traffic. It requires a specific, malformed request targeting the MPTCP MP_JOIN handshake mechanism. Connections that do not utilize the Fast Open feature for subflows do not trigger this error, as the issue is strictly tied to how the kernel attempts to combine these two incompatible networking features.

Is my system at risk if it is internet-facing?

While the vulnerability is network-reachable, Halo Surface Signal notes that exploitation is unlikely. The issue requires an attacker to interact with the complex MPTCP MP_JOIN handshake process rather than a typical web or management service. It is most relevant to systems specifically configured to support these advanced MPTCP subflow features rather than general-purpose servers.

What is the first step to address this kernel issue?

The priority is to inventory your infrastructure to identify which systems are running a kernel version with MPTCP enabled. Once identified, coordinate with your platform and infrastructure teams to verify if your network configuration utilizes MP_JOIN subflows. If MPTCP is active, plan to apply the official kernel security updates provided by your distribution maintainer during your next maintenance window.

References