# CVE-2026-90345: wifi: brcmfmac: fix P2P action frame handling without device vif

> A null pointer dereference in the brcmfmac Wi-Fi driver allows local attackers to cause a system crash via crafted P2P action frames.

- **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:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102779, BELL-CVE-2026-90345, DEBIAN-CVE-2026-90345, GHSA-4cvp-2fxw-jr85, UBUNTU-CVE-2026-90345

## What is CVE-2026-90345?

CVE-2026-90345 is a vulnerability in Linux, published on 17 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: brcmfmac: fix P2P action frame handling without device vif

Some P2P action frame paths assume the P2P device vif is always
available. That is not true when userspace sends non-P2P public action
frames through the primary interface, or when action-frame abort runs
after the P2P device vif has not been created.

Fall back to the primary vif when aborting an action frame without a P2P
device vif, and guard P2P device saved IE access before using it for
peer channel search.

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


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

Apply the vendor's patch.

## Is CVE-2026-90345 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90345 is a vulnerability in Linux, published on 17 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-90345 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-90345/ (Markdown: https://insights.sbomify.com/CVE-2026-90345/index.md)
```

## Sources

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

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