CVE-2026-97432wifi: iwlwifi: mvm: fix P2P-Device binding handling
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 27 days later
· 27 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 64c277f6329818db3124c9759cb9acf0f6070a54 – < 50bf37362362c8f03ab1aeab866b7fb08b262204
- affected 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 – < 8575514a979490c9d4517fcf19b4e19119c27702
- affected 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 – < 7be2fc679c8f657868988e41c0bb15bf5a454620
- affected 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77 – < b74e377cad9271950c57472867c469e4b5b2ff0c
- affected 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8
- affected 6.6.2 – < 6.6.160
- affected 6.5.12 – < 6.6
- affected 6.7
- unaffected < 6.7
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/50bf37362362c8f03ab1aeab866b7fb08b262204 (opens in a new tab)
- https://git.kernel.org/stable/c/8575514a979490c9d4517fcf19b4e19119c27702 (opens in a new tab)
- https://git.kernel.org/stable/c/7be2fc679c8f657868988e41c0bb15bf5a454620 (opens in a new tab)
- https://git.kernel.org/stable/c/b74e377cad9271950c57472867c469e4b5b2ff0c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86045 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97432)Record last updated .