wifi: iwlwifi: mvm: fix P2P-Device binding handling
Summary
| CVE | CVE-2026-97432 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-24 17:17:21 UTC |
| Updated | 2026-10-21 13:21:09 UTC |
| 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. |
Risk And Classification
EPSS: 0.001550000 probability, percentile 0.043320000 (date 2026-10-21)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 64c277f6329818db3124c9759cb9acf0f6070a54 50bf37362362c8f03ab1aeab866b7fb08b262204 git | Not specified |
| CNA | Linux | Linux | affected 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 8575514a979490c9d4517fcf19b4e19119c27702 git | Not specified |
| CNA | Linux | Linux | affected 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 7be2fc679c8f657868988e41c0bb15bf5a454620 git | Not specified |
| CNA | Linux | Linux | affected 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 b74e377cad9271950c57472867c469e4b5b2ff0c git | Not specified |
| CNA | Linux | Linux | affected 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8 git | Not specified |
| CNA | Linux | Linux | affected 6.6.2 6.6.160 semver | Not specified |
| CNA | Linux | Linux | affected 6.5.12 6.6 semver | Not specified |
| CNA | Linux | Linux | affected 6.7 | Not specified |
| CNA | Linux | Linux | unaffected 6.7 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.114 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.53 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/7be2fc679c8f657868988e41c0bb15bf5a454620 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/50bf37362362c8f03ab1aeab866b7fb08b262204 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b74e377cad9271950c57472867c469e4b5b2ff0c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8575514a979490c9d4517fcf19b4e19119c27702 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.