CVE-2025-38552
Description
A flaw was found in the Linux kernel's Multipath TCP (MPTCP) subsystem. A race condition between subflow failure handling and concurrent subflow creation can result in a Denial of Service (DoS). A local user could exploit this flaw by triggering error signaling or connection fallback during precise timing windows, leading to system instability or a kernel crash.
Statement
This vulnerability is rated as Moderate severity because exploitation requires a local attacker to win precise timing races during Multipath TCP (MPTCP) connection state transitions, limiting the blast radius primarily to a denial of service without direct privilege escalation. Exploitation relies on concurrent subflow handling while the connection undergoes fallback or error signaling, which is difficult to reliably synchronize. Systems that do not utilize MPTCP or have the protocol disabled via kernel configuration are not exposed to this issue.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | 7.8 | 9.4 |
| Attack Vector | Local | Local | Network |
| Attack Complexity | High | Low | Low |
| Privileges Required | Low | Low | None |
| User Interaction | None | None | None |
| Scope | Unchanged | Unchanged | Unchanged |
| Confidentiality | None | High | Low |
| Integrity Impact | Low | High | High |
| Availability Impact | High | High | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
NVD: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.