mptcp: pm: kernel: drop pending ADD_ADDR when removing ID0
Summary
| CVE | CVE-2026-97566 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-25 11:17:07 UTC |
| Updated | 2026-10-21 13:21:13 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: kernel: drop pending ADD_ADDR when removing ID0 The in-kernel MPTCP path manager can leave a stale ADD_ADDR announcement entry alive when removing the id 0 endpoint. This happens because the id 0 removal path does not tear down pending announcements, unlike the non-zero id path. When the PM later reselects id 0 after adding another signal endpoint, it finds the stale anno_list entry and hits WARN_ON_ONCE(mptcp_pm_is_kernel()) in mptcp_pm_announced_alloc(). Root cause: asymmetry between removal paths. - Non-zero id path: mptcp_nl_remove_subflow_and_signal_addr() calls mptcp_pm_remove_announced() to clean up. - Id 0 path: mptcp_nl_remove_id_zero_address() skips cleanup entirely. Fix by making the id 0 path symmetric: call mptcp_pm_announced_remove() and decrement add_addr_signaled before queuing the RM_ADDR. Subtle detail: signal endpoints are stored in anno_list with port 0, but msk_local carries the connection's local port. In other words, entries linked to ID0 paths should have port == 0. A follow-up patch will ensure that. mptcp_pm_announced_remove() uses use_port=true for comparison. So clear the port before the lookup. |
Risk And Classification
EPSS: 0.002000000 probability, percentile 0.088970000 (date 2026-10-05)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 740d798e8767d8a449902b1a1bbc70facfce19b5 189d60057e5f3d6a62e3d71a3cc428c9150bc14f git | Not specified |
| CNA | Linux | Linux | affected 740d798e8767d8a449902b1a1bbc70facfce19b5 bacf23e7c9876c9f4170166b3597cb22ea3ed39b git | Not specified |
| CNA | Linux | Linux | affected 740d798e8767d8a449902b1a1bbc70facfce19b5 d4a67a880654e1bfe318a31bea0bdbb026a09ade git | Not specified |
| CNA | Linux | Linux | affected 740d798e8767d8a449902b1a1bbc70facfce19b5 545616b4e7325be3c61fc082538cb06d14f7b1db git | Not specified |
| CNA | Linux | Linux | affected 740d798e8767d8a449902b1a1bbc70facfce19b5 2ac7d6e620764f1fc79eb4edd3610a7a661981ca git | Not specified |
| CNA | Linux | Linux | affected 5.13 | Not specified |
| CNA | Linux | Linux | unaffected 5.13 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.112 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.7 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/2ac7d6e620764f1fc79eb4edd3610a7a661981ca | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d4a67a880654e1bfe318a31bea0bdbb026a09ade | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/189d60057e5f3d6a62e3d71a3cc428c9150bc14f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/545616b4e7325be3c61fc082538cb06d14f7b1db | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/bacf23e7c9876c9f4170166b3597cb22ea3ed39b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.