Security readout for executives and security teams
Plain-English summary
A Linux Multipath TCP flaw can corrupt connection-management accounting when an address is removed. On affected systems using MPTCP, a remote, unauthenticated network peer may cause substantial service disruption and limited integrity impact. Ordinary TCP workloads that do not use MPTCP are less likely to encounter the vulnerable path.
Executive priority
Prioritize remediation for internet-facing or business-critical Linux systems using MPTCP. The potential availability impact is high, but urgency can be reduced for systems where MPTCP is disabled or unreachable. Require asset owners to verify vendor backport status rather than relying only on kernel version strings.
Technical view
The MPTCP path manager incorrectly decrements add_addr_accepted after receiving RM_ADDR for some subflows not created through ADD_ADDR. The correction limits decrementing to qualifying MP_JOIN subflows with a nonzero remote ID initiated by the RM_ADDR recipient. The supplied CVSS 3.1 score is 8.2: network-accessible, low complexity, no privileges or user interaction, with high availability impact.
Likely exposure
Exposure is concentrated in Linux hosts where MPTCP is available and actively used by reachable peers. The bundle lists affected Linux versions or branches including 5.10, 5.15.167, 6.1.107, 6.6.48, 6.10.7, and 6.11, but its version data is ambiguous; confirm exact vendor package status and backports.
Exploitation context
The CVSS vector indicates a remotely reachable, unauthenticated condition with low attack complexity. However, the supplied record is not in KEV and provides no evidence of exploitation in the wild or a public exploit. Treat exploitation status as unconfirmed rather than active.
Researcher notes
The fault was identified through the mptcp_join.sh “remove single subflow” self-test and concerns counter handling across RM_ADDR and subflow closure. The sources establish the corrected logic but do not identify a CWE, demonstrate practical exploitation, or fully clarify affected-version ranges. Distribution-specific assessment is therefore necessary.
Mitigation direction
- Install a vendor-supported kernel update incorporating the applicable upstream stable correction.
- Prioritize reachable systems that actively enable or depend on MPTCP.
- If immediate patching is impossible, assess whether MPTCP can be disabled without operational impact.
- Check distribution advisories because kernel fixes are commonly backported without matching upstream version numbers.
Validation and detection
- Record the running kernel package and distribution release on each potentially exposed host.
- Determine whether MPTCP is enabled, used, and reachable from untrusted networks.
- Compare vendor package changelogs against CVE-2024-45009 and the referenced stable commits.
- After updating, confirm the active kernel contains the vendor fix and rerun relevant MPTCP regression tests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-45009 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H3.94.2LinuxVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/35b31f5549ede4070566b949781e83495906b43dCVE reference, Linux
- https://git.kernel.org/stable/c/85b866e4c4e63a1d7afb58f1e24273caad03d0b7CVE reference, Linux
- https://git.kernel.org/stable/c/d20bf2c96d7ffd171299b32f562f70e5bf5dc608CVE reference, Linux
- https://git.kernel.org/stable/c/2060f1efab370b496c4903b840844ecaff324c3cCVE reference, Linux
- https://git.kernel.org/stable/c/1c1f721375989579e46741f59523e39ec9b2a9bdCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.