PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-97566 Linux CVE debrief

A vulnerability in the Linux kernel's MPTCP path manager has been resolved. The in-kernel MPTCP path manager can leave a stale ADD_ADDR announcement entry alive when removing the id 0 endpoint, leading to a WARN_ON_ONCE(mptcp_pm_is_kernel()) in mptcp_pm_announced_alloc(). This occurs due to asymmetry between removal paths for non-zero and id 0 endpoints. The non-zero id path calls mptcp_pm_remove_announced() to clean up, while the id 0 path does not. To fix this, the id 0 path should be made symmetric by calling mptcp_pm_announced_remove() and decrementing add_addr_signaled before queuing the RM_ADDR.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-25
Original CVE updated
2026-09-25
Advisory published
2026-09-25
Advisory updated
2026-09-25

Who should care

Linux kernel developers and administrators responsible for maintaining and securing Linux-based systems should assess exposure and verify kernel versions. They should review system configurations, monitor system logs, and perform vulnerability management to ensure the MPTCP path manager is properly configured and secured.

Why it matters

A vulnerability in the Linux kernel's MPTCP path manager can lead to WARN_ON_ONCE(mptcp_pm_is_kernel()) errors. Defenders should verify kernel versions, review system configurations, and monitor system logs.

  • Verify kernel updates to ensure MPTCP path manager is properly cleaning up ADD_ADDR announcements
  • Monitor system logs for WARN_ON_ONCE(mptcp_pm_is_kernel()) errors
  • Review system configurations for MPTCP path manager

Technical summary

The Linux kernel's MPTCP path manager can leave a stale ADD_ADDR announcement entry alive when removing the id 0 endpoint. This can lead to a WARN_ON_ONCE(mptcp_pm_is_kernel()) in mptcp_pm_announced_alloc(). The issue is caused by asymmetry between removal paths for non-zero and id 0 endpoints. The non-zero id path calls mptcp_pm_remove_announced() to clean up, while the id 0 path does not. To fix this, the id 0 path should be made symmetric by calling mptcp_pm_announced_remove() and decrementing add_addr_signaled before queuing the RM_ADDR. This change ensures that the MPTCP path manager properly cleans up ADD_ADDR announcements.

Defensive priority

Verify and apply kernel updates to ensure MPTCP path manager is properly cleaning up ADD_ADDR announcements.

Recommended defensive actions

  • Verify kernel version and apply updates if necessary
  • Review system configurations for MPTCP path manager
  • Monitor system logs for WARN_ON_ONCE(mptcp_pm_is_kernel()) errors
  • Perform a thorough review of system configurations and MPTCP path manager settings
  • Check for any exposed assets that may require extra review
  • Track exceptions and retest remediated assets
  • Document evidence of remediation

Evidence notes

The CVE record and source references indicate a vulnerability in the Linux kernel's MPTCP path manager. However, details on exploitation, impact, and remediation are limited. Defenders should verify kernel versions, review system configurations, and monitor system logs for potential issues. The source provides a brief description of the vulnerability and its resolution, but further analysis is needed to fully understand the vulnerability's impact.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-97566 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-97566

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-97566 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97566

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/2ac7d6e620764f1fc79eb4edd3610a7a661981ca

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/545616b4e7325be3c61fc082538cb06d14f7b1db

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/d4a67a880654e1bfe318a31bea0bdbb026a09ade

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.