CVE-2026-97566mptcp: pm: kernel: drop pending ADD_ADDR when removing ID0
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 35 days later
· 35 days 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 740d798e8767d8a449902b1a1bbc70facfce19b5 – < 4af59a98aead422a152d805a89586dbb65616fc8
- affected 740d798e8767d8a449902b1a1bbc70facfce19b5 – < 189d60057e5f3d6a62e3d71a3cc428c9150bc14f
- affected 740d798e8767d8a449902b1a1bbc70facfce19b5 – < bacf23e7c9876c9f4170166b3597cb22ea3ed39b
- affected 740d798e8767d8a449902b1a1bbc70facfce19b5 – < d4a67a880654e1bfe318a31bea0bdbb026a09ade
- affected 740d798e8767d8a449902b1a1bbc70facfce19b5 – < 545616b4e7325be3c61fc082538cb06d14f7b1db
- affected 740d798e8767d8a449902b1a1bbc70facfce19b5 – < 2ac7d6e620764f1fc79eb4edd3610a7a661981ca
- affected 5.13
- unaffected < 5.13
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/4af59a98aead422a152d805a89586dbb65616fc8 (opens in a new tab)
- https://git.kernel.org/stable/c/189d60057e5f3d6a62e3d71a3cc428c9150bc14f (opens in a new tab)
- https://git.kernel.org/stable/c/bacf23e7c9876c9f4170166b3597cb22ea3ed39b (opens in a new tab)
- https://git.kernel.org/stable/c/d4a67a880654e1bfe318a31bea0bdbb026a09ade (opens in a new tab)
- https://git.kernel.org/stable/c/545616b4e7325be3c61fc082538cb06d14f7b1db (opens in a new tab)
- https://git.kernel.org/stable/c/2ac7d6e620764f1fc79eb4edd3610a7a661981ca (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86874 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97566)Record last updated .