Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-45009

mptcp: pm: only decrement add_addr_accepted for MPJ req

Description

In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: only decrement add_addr_accepted for MPJ req Adding the following warning ... WARN_ON_ONCE(msk->pm.add_addr_accepted == 0) ... before decrementing the add_addr_accepted counter helped to find a bug when running the "remove single subflow" subtest from the mptcp_join.sh selftest. Removing a 'subflow' endpoint will first trigger a RM_ADDR, then the subflow closure. Before this patch, and upon the reception of the RM_ADDR, the other peer will then try to decrement this add_addr_accepted. That's not correct because the attached subflows have not been created upon the reception of an ADD_ADDR. A way to solve that is to decrement the counter only if the attached subflow was an MP_JOIN to a remote id that was not 0, and initiated by the host receiving the RM_ADDR.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-45009, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.2CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.52% · top 55% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

  • Linux · Linux

    • affected d0876b2284cf8b34dd214b2d0aa21071c345da59 – < 35b31f5549ede4070566b949781e83495906b43d
    • affected d0876b2284cf8b34dd214b2d0aa21071c345da59 – < 85b866e4c4e63a1d7afb58f1e24273caad03d0b7
    • affected d0876b2284cf8b34dd214b2d0aa21071c345da59 – < d20bf2c96d7ffd171299b32f562f70e5bf5dc608
    • affected d0876b2284cf8b34dd214b2d0aa21071c345da59 – < 2060f1efab370b496c4903b840844ecaff324c3c
    • affected d0876b2284cf8b34dd214b2d0aa21071c345da59 – < 1c1f721375989579e46741f59523e39ec9b2a9bd
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.15.167 – ≤ 5.15.*
    • unaffected 6.1.107 – ≤ 6.1.*
    • unaffected 6.6.48 – ≤ 6.6.*
    • unaffected 6.10.7 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-45009 badge
[![CVE-2024-45009](https://cveledger.app/badge/CVE-2024-45009.svg)](https://cveledger.app/cve/CVE-2024-45009)

Record last updated .