CVE-2024-45009

mptcp: pm: only decrement add_addr_accepted for MPJ req

MEDIUM
5.5
CVSS Score
Published: September 11, 2024 at 03:13 PM UTC
Updated: August 5, 2026 at 12:04 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10 ≤ v < 5.15.1675.10 ≤ v < 6.1.1075.10 ≤ v < 6.10.75.10 ≤ v < 6.115.10 ≤ v < 6.6.485.16 ≤ v < 6.1.1076.2 ≤ v < 6.6.486.7 ≤ v < 6.10.76.11 rc16.11 rc26.11 rc36.11 rc4d0876b2284cf8b34dd214b2d0aa21071c345da59
Vendor states this is fixed in 1c1f721375989579e46741f59523e39ec9b2a9bd (fixed)
Vendor states this is fixed in 2060f1efab370b496c4903b840844ecaff324c3c (fixed)
Vendor states this is fixed in 35b31f5549ede4070566b949781e83495906b43d (fixed)
Vendor states this is fixed in 85b866e4c4e63a1d7afb58f1e24273caad03d0b7 (fixed)
Vendor states this is fixed in d20bf2c96d7ffd171299b32f562f70e5bf5dc608 (fixed)
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 5.15.167 (unaffected)
Vendor states this is fixed in 6.1.107 (unaffected)
Vendor states this is fixed in 6.10.7 (unaffected)
Vendor states this is fixed in 6.11 (unaffected)
Vendor states this is fixed in 6.6.48 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1c1f721375989579e46741f59523e39ec9b2a9bd
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2060f1efab370b496c4903b840844ecaff324c3c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/35b31f5549ede4070566b949781e83495906b43d
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/85b866e4c4e63a1d7afb58f1e24273caad03d0b7
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d20bf2c96d7ffd171299b32f562f70e5bf5dc608
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card