CVE-2026-97567

Description

A flaw was found in the Linux kernel's MultiPath TCP (MPTCP) subsystem. A race condition can occur between socket disconnection and packet retransmission timer handling, resulting in an inconsistent socket state. A local user can exploit this timing flaw during active connection teardown to cause a system crash, leading to a Denial of Service (DoS).

Statement

A race condition flaw, rated Moderate by Red Hat Product Security, was found in the Linux kernel's MultiPath TCP (MPTCP) implementation. The MPTCP socket disconnect() operation and the retransmission (rtx) timer handling can race because the timer was not stopped synchronously during disconnect, which can leave the socket in an inconsistent state. A local user able to create and disconnect MPTCP sockets could trigger this race during active connection teardown, causing a system crash and resulting in a denial of service. The flaw does not affect confidentiality or integrity.

The vulnerable full MPTCP disconnect implementation was introduced upstream in Linux 5.17 and is present in Red Hat Enterprise Linux 9 and later based kernels. Red Hat Enterprise Linux 6, 7, and 8 (including their real-time kernel variants) and OpenShift Container Platform 4.12 (RHEL CoreOS 8) are not affected because the vulnerable code is not present in those kernels. Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform 4.13 and later releases based on RHEL CoreOS 9 are affected.

The fix for the affected products has been deferred to a future update. The residual risk is limited: exploitation requires local access to an MPTCP socket, depends on the timing between the disconnect operation and the retransmission timer callback, and the worst case is a system crash (local denial of service) with no impact on confidentiality or integrity.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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 Score5.5N/AN/A
Attack VectorLocalN/AN/A
Attack ComplexityLowN/AN/A
Privileges RequiredLowN/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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Integrity,Other

Technical Impact: Alter Execution Logic; Unexpected State

The main problem is that -- if a lock is overcome -- data could be altered in a bad state.

Frequently Asked Questions

Want to get errata notifications? Sign up here.