CVE-2026-98340: Linux kernel · wifi: cfg80211: only group hidden BSSes with beacon entries
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 3658093df69849daf4f813a8f087f358e13be203 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3658093df69849daf4f813a8f087f358e13be203, 86235be788094131912e9bd8412b358d91d99f49, 73365b81630b57e1a1f9d50dc87281797855c2ac +5
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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix has been implemented and is available in the Linux kernel commits identified by the fixedVersions hashes. Users should update their Linux kernel to a version including these fixes to resolve the issue.
Description
A vulnerability in the Linux kernel's wifi cfg80211 subsystem involved improper grouping of hidden BSS entries without beacon elements. This could cause internal warnings due to unexpected grouping behavior when probe responses and beacons are processed. The issue has been resolved by ensuring only entries with beacon information are grouped, preventing the problematic state.
References
- git.kernel.org/stable/c/4cd6a518ce7527284bbc9baab5fa2453a7d477c2 (opens in a new tab)
- git.kernel.org/stable/c/74ed0d992f392c75e1969415527e06df3f7a4034 (opens in a new tab)
- git.kernel.org/stable/c/3658093df69849daf4f813a8f087f358e13be203 (opens in a new tab)
- git.kernel.org/stable/c/73365b81630b57e1a1f9d50dc87281797855c2ac (opens in a new tab)
- git.kernel.org/stable/c/7405dd19bda4537a2843637d8d7bed1efd4776cf (opens in a new tab)
- git.kernel.org/stable/c/86235be788094131912e9bd8412b358d91d99f49 (opens in a new tab)
- git.kernel.org/stable/c/332ea1502c46f53375cb109fa82bfaff818f3a41 (opens in a new tab)
- git.kernel.org/stable/c/068843ed0902c552a13860c5ec6b2ca65b57a065 (opens in a new tab)