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

> A logic error in the iwlwifi driver causes a firmware crash when P2P-Device bindings are improperly re-added, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-103907, BELL-CVE-2026-97432, DEBIAN-CVE-2026-97432, GHSA-w9g9-vhwv-w598, UBUNTU-CVE-2026-97432

## What is CVE-2026-97432?

CVE-2026-97432 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-97432?


## How do I fix CVE-2026-97432?

Apply the vendor's patch.

## Is CVE-2026-97432 being exploited?

There is no known exploitation of CVE-2026-97432 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97432 and fix it if it is affected.

What it is: CVE-2026-97432 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97432 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97432/ (Markdown: https://insights.sbomify.com/CVE-2026-97432/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97432
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97432
- OSV: https://osv.dev/vulnerability/CVE-2026-97432

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97432/
Summaries are generated and may contain mistakes; the official description above is the record.