What’s Vulnerable › Vulnerabilities
CVE-2026-97432: wifi: iwlwifi: mvm: fix P2P-Device binding handling
- Severity: unknown
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-09-24 · updated 2026-10-21
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.
Affected products
- Linux kernel: from 6.6.2 before 6.6.160; from 6.5.12 before 6.6; 6.7 — fixed in 6.6, 6.6.160, 7.2
How to fix
Upgrade to a fixed version: Linux kernel 6.6, 6.6.160, 7.2. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/50bf37362362c8f03ab1aeab866b7fb08b262204
- https://git.kernel.org/stable/c/7be2fc679c8f657868988e41c0bb15bf5a454620
- https://git.kernel.org/stable/c/8575514a979490c9d4517fcf19b4e19119c27702
- https://git.kernel.org/stable/c/b74e377cad9271950c57472867c469e4b5b2ff0c
Get alerted when CVE-2026-97432 or the next vulnerability affects your stack