CVE-2026-97432

wifi: iwlwifi: mvm: fix P2P-Device binding handling

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: fix P2P-Device binding handling Our binding handling for P2P-Device can run into the following scenario, as observed by our testing: - a station interface is connected on some channel - the P2P-Device does a remain-on-channel (ROC) on that channel - the ROC ends, and the P2P-Device is removed from the binding, but the phy_ctxt pointer is left around as a PHY cache so we don't need to recalibrate to the channel again and again in case it's not shared - a binding update by the station interface, even a removal, will re-add the P2P-Device to the binding - the P2P-Device is removed, which removes the PHY context, but it's still in the binding so the firmware crashes Since the P2P device is removed from the binding and only re- added by unrelated code, but we want to keep the phy_ctxt around as a cache for future ROC usage, fix it by adding a boolean that indicates whether or not the P2P-Device should be added to the binding, and handle that in the binding iterator. That way, the station interface cannot re-add the P2P-Device to the binding when that isn't active.

Key facts

Published
24 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.246% 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
  • 64c277f6329818db3124c9759cb9acf0f6070a54 up to but excluding 50bf37362362c8f03ab1aeab866b7fb08b262204 (affected)
  • 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 up to but excluding 8575514a979490c9d4517fcf19b4e19119c27702 (affected)
  • 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 up to but excluding 7be2fc679c8f657868988e41c0bb15bf5a454620 (affected)
  • 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 up to but excluding b74e377cad9271950c57472867c469e4b5b2ff0c (affected)
  • 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8 (affected)
  • 6.6.2 up to but excluding 6.6.160 (affected)
  • 6.5.12 up to but excluding 6.6 (affected)
LinuxLinux
  • Default status: affected
  • 6.7 (affected)
  • 0 up to but excluding 6.7 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References