# CVE-2026-98350: wifi: brcmfmac: cyw: pass PMKID to firmware if present

> An attacker within Wi-Fi range can read uninitialized kernel stack memory leaked to firmware due to improper initialization in the brcmfmac driver.

- **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:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98350, DEBIAN-CVE-2026-98350, GHSA-c6xm-v6x8-64wh, UBUNTU-CVE-2026-98350

## What is CVE-2026-98350?

CVE-2026-98350 is a vulnerability in Linux, published on 6 Oct 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: cyw: pass PMKID to firmware if present

Zero out auth_status on initialization. Otherwise, garbage will
leak from the stack to the firmware (when ssid is less than 32 bytes
and/or when params->pmkid is set). Then, pass the params->pmkid to the
firmware (without it, the firmware caches a garbage PMKID on successful
authentication and denies a subsequent association request that includes
the PMKID).

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


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

Apply the vendor's patch.

## Is CVE-2026-98350 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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