CVE-2026-97432

published 24 Sep 2026 · updated 17 Nov 2026

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

5.1MediumCVSS 5.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b74e377cad9271950c57472867c469e4b5b2ff0c, Kernel 6.6.160, Kernel 50bf37362362c8f03ab1aeab866b7fb08b262204 and 5 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 <b74e377cad9271950c57472867c469e4b5b2ff0c, >=6.6.2 <6.6.160, >=64c277f6329818db3124c9759cb9acf0f6070a54 <50bf37362362c8f03ab1aeab866b7fb08b262204, >=84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 <7be2fc679c8f657868988e41c0bb15bf5a454620, >=84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 <8575514a979490c9d4517fcf19b4e19119c27702, =6.7, =8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8, >=6.5.12 <6.6b74e377cad9271950c57472867c469e4b5b2ff0c, 6.6.160, 50bf37362362c8f03ab1aeab866b7fb08b262204, 7be2fc679c8f657868988e41c0bb15bf5a454620, 8575514a979490c9d4517fcf19b4e19119c27702, 6.6
linux-kernel: Kernel>=6.5.12 <6.6, >=6.6.2 <6.6.160, >=6.7.0 <6.12.114, >=6.13.0 <6.18.536.6, 6.6.160, 6.12.114, 6.18.53

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97432 severity on Zeptric[![CVE-2026-97432](https://zeptric.io/badge/cve/CVE-2026-97432.svg)](https://zeptric.io/cve/CVE-2026-97432)