CVE-2026-97432
Last modified
CVE-2026-97432 is a vulnerability of currently unknown severity. 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..
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, < 7be2fc679c8f657868988e41c0bb15bf5a454620; >= 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, < b74e377cad9271950c57472867c469e4b5b2ff0c; 8ddf2212cfa5d9ef4fd289ce0d9dda728f2160b8; 64c277f6329818db3124c9759cb9acf0f6070a54; >= 6.5.12, < 6.6; >= 6.6.2, < 6.7 |
| Linux | Linux | 6.7 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97432?
How severe is CVE-2026-97432?
How do I fix CVE-2026-97432?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97427In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97428In the Linux kernel, the following vulnerability has been re…7.7
- CVE-2026-97429In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-9743In MongoDB Server 8.0, an aggregation stage can leave its _s…7.1
- CVE-2026-97430In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97431In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97433In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-97434In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97435In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97436In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97437In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-97438In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-97432?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
