CVE-2024-27404: mptcp: fix data races on remote_id
In the Linux kernel, the following vulnerability has been resolved:
mptcp: fix data races on remote_id
Similar to the previous patch, address the data race on
remote_id, adding the suitable ONCE annotations.
Security readout for executives and security teams
Plain-English summary
A race condition in Linux Multipath TCP (MPTCP) can cause inconsistent handling of a remote endpoint identifier. The supplied CVSS assessment indicates a remote, unauthenticated attacker could primarily disrupt availability and potentially cause limited integrity impact. The bundle does not describe confidentiality loss.
Executive priority
Treat as a high-priority availability risk, especially for exposed or business-critical Linux services using MPTCP. Validate applicability promptly, then patch through supported distribution channels. Immediate emergency action is not supported by the supplied exploitation evidence.
Technical view
Concurrent access to MPTCP's remote_id lacked suitable one-time access annotations, creating a data race. Linux stable fixes add the required ONCE annotations. CVSS 3.1 is 8.2: network-accessible, low complexity, no privileges or user interaction, with high availability and low integrity impact.
Likely exposure
Exposure concerns Linux systems containing the affected MPTCP implementation. The bundle lists 6.0, 6.1.81, 6.6.19, 6.7.7, and 6.8, but does not clearly express version ranges. Confirm distribution backports and whether MPTCP is enabled, used, or network-reachable.
Exploitation context
The source bundle marks this CVE as absent from CISA KEV and provides no evidence of active exploitation or a public exploit. Its CVSS vector describes remote, unauthenticated, low-complexity attack potential, but the supplied description does not document triggering conditions or observed attacks.
Researcher notes
The record is narrowly scoped to a remote_id data race and its ONCE annotations. It does not identify the precise race outcome, affected call paths, triggering prerequisites, or exploit reliability. Version data is ambiguous, so commit-level or distribution-advisory verification is necessary.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable Linux stable fix.
Check distribution security advisories because package versions may include backported fixes.
Reduce unnecessary MPTCP exposure until remediation if operationally feasible.
Prioritize internet-facing or availability-critical systems after confirming applicability.
Validation and detection
Record each system's running kernel and distribution package version.
Check package changelogs for CVE-2024-27404 or a referenced stable commit.
Confirm whether MPTCP is enabled, used, and reachable in the deployed configuration.
Reboot after upgrading and verify the fixed kernel is running.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27404 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.