CVE-2026-98350: Linux kernel · wifi: brcmfmac: cyw: pass PMKID to firmware if present
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e2de8d5eb2984416affdd9559e55f37c7f1bbf47 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 16:39 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e2de8d5eb2984416affdd9559e55f37c7f1bbf47, c2cf589c7d546557ed60c43f2ec014279265dfbf, 6fba6233e9ca7718661e53555a3961c58772c21a
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to e2de8d5eb2984416affdd9559e55f37c7f1bbf47, c2cf589c7d546557ed60c43f2ec014279265dfbf or 6fba6233e9ca7718661e53555a3961c58772c21a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel. Users should update to a fixed kernel version that includes the patches identified by commits e2de8d5eb2984416affdd9559e55f37c7f1bbf47, c2cf589c7d546557ed60c43f2ec014279265dfbf, and 6fba6233e9ca7718661e53555a3961c58772c21a. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's brcmfmac driver for Broadcom Wi-Fi chips was fixed by ensuring the PMKID is properly passed to firmware and auth_status is zeroed on initialization. Without this fix, garbage data could leak from the stack to the firmware, causing the firmware to cache invalid PMKIDs and deny valid association requests.