Answer in brief
CVE-2024-45009 records a High severity (CVSS 8.2) vulnerability in mptcp: pm: only decrement add_addr_accepted for MPJ req. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d0876b2284cf8b34dd214b2d0aa21071c345da59 <35b31f5549ede4070566b949781e83495906b43d || >=d0876b2284cf8b34dd214b2d0aa21071c345da59 <85b866e4c4e63a1d7afb58f1e24273caad03d0b7 || >=d0876b2284cf8b34dd214b2d0aa21071c345da59 <d20bf2c96d7ffd171299b32f562f70e5bf5dc608 || >=d0876b2284cf8b34dd214b2d0aa21071c345da59 <2060f1efab370b496c4903b840844ecaff324c3c || >=d0876b2284cf8b34dd214b2d0aa21071c345da59 <1c1f721375989579e46741f59523e39ec9b2a9bd | 35b31f5549ede4070566b949781e83495906b43d, 85b866e4c4e63a1d7afb58f1e24273caad03d0b7, d20bf2c96d7ffd171299b32f562f70e5bf5dc608, 2060f1efab370b496c4903b840844ecaff324c3c, 1c1f721375989579e46741f59523e39ec9b2a9bd |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Sep 11, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.