CVE-2026-80587
Description
A flaw was found in the Multipath TCP (MPTCP) implementation within the Linux kernel. This vulnerability arises from the kernel's handling of mutually exclusive MPTCP suboptions. A remote attacker could send specially crafted MPTCP suboptions that, when combined, are not expected by the kernel. This could lead to the kernel ignoring the conflicting suboptions and stopping their processing, potentially causing unexpected network behavior or a denial of service.
Statement
A moderate impact flaw was found in the Linux kernel's Multipath TCP (MPTCP) implementation as shipped in Red Hat Enterprise Linux 8, 9, and 10 (kernel and kernel-rt) and Red Hat In-Vehicle OS. The MPTCP input path did not validate combinations of MPTCP suboptions that RFC 8684 defines as mutually exclusive, and the code does not expect such combinations to be present. A remote attacker able to reach an MPTCP-enabled endpoint could send specially crafted packets containing conflicting or unexpected suboption combinations, causing the kernel to ignore the extra suboptions and stop processing them, which can lead to unexpected network behavior or a denial of service for the affected MPTCP connections. The impact is limited to availability: conflicting suboptions are ignored and their processing stops, and there is no evidence of memory corruption, information disclosure, or privilege escalation. Red Hat Enterprise Linux 6 and 7 are not affected because the vulnerable MPTCP code is not present in those releases. The fix has been deferred for the affected Red Hat Enterprise Linux and Red Hat In-Vehicle OS streams; the residual risk is a connection-level denial of service limited to systems with MPTCP enabled and exposed to untrusted peers. Red Hat rates this flaw Moderate (CVSS 5.5, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), substantially lower than the upstream CVEORG critical rating of 9.8, because the practical effect is confined to availability of individual MPTCP connections rather than confidentiality or integrity impact.
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 Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 9.8 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Other
Technical Impact: Varies by Context
When complex inputs are inconsistent, attackers could trigger unexpected errors, cause incorrect actions to take place, or exploit latent vulnerabilities.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.