Skip to main content
VulnerabilityPublished Updated

CVE-2026-97566: Linux kernel · mptcp: pm: kernel: drop pending ADD_ADDR when removing ID0

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97566· Low

Not known to be exploited · fixed in d4a67a880654e1bfe318a31bea0bdbb026a09ade : update Linux kernel when convenient.

Data as of 30 Oct 2026, 17:48 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d4a67a880654e1bfe318a31bea0bdbb026a09ade, bacf23e7c9876c9f4170166b3597cb22ea3ed39b, 545616b4e7325be3c61fc082538cb06d14f7b1db +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 740d798e8767d8a449902b1a1bbc70facfce19b5, < d4a67a880654e1bfe318a31bea0bdbb026a09ade
Fixed in
  • d4a67a880654e1bfe318a31bea0bdbb026a09ade
LinuxLinuxAffected
  • ≥ 740d798e8767d8a449902b1a1bbc70facfce19b5, < bacf23e7c9876c9f4170166b3597cb22ea3ed39b
Fixed in
  • bacf23e7c9876c9f4170166b3597cb22ea3ed39b
LinuxLinuxAffected
  • ≥ 740d798e8767d8a449902b1a1bbc70facfce19b5, < 545616b4e7325be3c61fc082538cb06d14f7b1db
Fixed in
  • 545616b4e7325be3c61fc082538cb06d14f7b1db
LinuxLinuxAffected
  • ≥ 740d798e8767d8a449902b1a1bbc70facfce19b5, < 189d60057e5f3d6a62e3d71a3cc428c9150bc14f
Fixed in
  • 189d60057e5f3d6a62e3d71a3cc428c9150bc14f
LinuxLinuxAffected
  • ≥ 740d798e8767d8a449902b1a1bbc70facfce19b5, < 4af59a98aead422a152d805a89586dbb65616fc8
Fixed in
  • 4af59a98aead422a152d805a89586dbb65616fc8
LinuxLinuxAffected
  • ≥ 740d798e8767d8a449902b1a1bbc70facfce19b5, < 2ac7d6e620764f1fc79eb4edd3610a7a661981ca
Fixed in
  • 2ac7d6e620764f1fc79eb4edd3610a7a661981ca

AI-suggested

A fix has been implemented that makes the ID0 removal path symmetric with the non-zero ID path by properly cleaning up pending ADD_ADDR announcements. Users should apply the official kernel update containing this fix once available. Patch status is not explicitly confirmed in the input; therefore, check the vendor advisory for current remediation guidance.

Description

A vulnerability in the Linux kernel's MPTCP path manager causes a stale ADD_ADDR announcement entry to remain when removing the ID0 endpoint. This occurs because the removal path for ID0 does not clean up pending announcements, unlike the non-zero ID path. This asymmetry can lead to kernel warnings when the path manager later reselects ID0 after adding another signal endpoint. The issue has been fixed by making the ID0 removal path symmetric and properly cleaning up the announcement entries.

References

Community reviews

Loading reviews…