CVE-2026-97566

mptcp: pm: kernel: drop pending ADD_ADDR when removing ID0

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.

Key facts

Published
25 Sep 2026
Last changed
30 Oct 2026
Assigned by
Linux
EPSS
0.212% likely to be exploited in the next 30 days, higher than 11.556% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 740d798e8767d8a449902b1a1bbc70facfce19b5 up to but excluding 4af59a98aead422a152d805a89586dbb65616fc8 (affected)
  • 740d798e8767d8a449902b1a1bbc70facfce19b5 up to but excluding 189d60057e5f3d6a62e3d71a3cc428c9150bc14f (affected)
  • 740d798e8767d8a449902b1a1bbc70facfce19b5 up to but excluding bacf23e7c9876c9f4170166b3597cb22ea3ed39b (affected)
  • 740d798e8767d8a449902b1a1bbc70facfce19b5 up to but excluding d4a67a880654e1bfe318a31bea0bdbb026a09ade (affected)
  • 740d798e8767d8a449902b1a1bbc70facfce19b5 up to but excluding 545616b4e7325be3c61fc082538cb06d14f7b1db (affected)
  • 740d798e8767d8a449902b1a1bbc70facfce19b5 up to but excluding 2ac7d6e620764f1fc79eb4edd3610a7a661981ca (affected)
LinuxLinux
  • Default status: affected
  • 5.13 (affected)
  • 0 up to but excluding 5.13 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References