CVE-2026-99634

Description

A flaw was found in the Linux kernel's Multipath TCP (MPTCP) implementation. When processing a subflow join request utilizing TCP Fast Open (TFO), the kernel fails to check whether an allocated child socket was marked for destruction during handshake fallback and queues it for acceptance. A remote attacker could exploit this vulnerability by sending a specially crafted connection request to trigger a use-after-free condition, potentially resulting in arbitrary code execution or a Denial of Service (DoS).

Statement

This vulnerability is rated as an Important impact because an unauthenticated remote attacker can trigger kernel memory corruption leading to a denial of service or potential code execution without requiring local privileges. The issue specifically affects systems running Linux kernels with Multipath TCP (MPTCP) handling incoming subflow connections with TCP Fast Open. In standard Red Hat Enterprise Linux installations, MPTCP is disabled by default, which restricts exposure to environments where administrators or network services have explicitly enabled the protocol.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score7.5N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Confidentiality

Technical Impact: Read Memory

If the expired pointer is used in a read operation, an attacker might be able to control data read in by the application.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If the expired pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" (such as NULL) or larger than expected by a read or write operation, then a crash may occur.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If the expired pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Frequently Asked Questions

Want to get errata notifications? Sign up here.