CVE-2026-98340
wifi: cfg80211: only group hidden BSSes with beacon entries
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 4593c4cbe1c96b3995727dc42f6aa103f4ff5afc, < 4cd6a518ce7527284bbc9baab5fa2453a7d477c2Upgrade to: 4cd6a518ce7527284bbc9baab5fa2453a7d477c2Affected: ≥ 4593c4cbe1c96b3995727dc42f6aa103f4ff5afc, < 74ed0d992f392c75e1969415527e06df3f7a4034Upgrade to: 74ed0d992f392c75e1969415527e06df3f7a4034Affected: ≥ 4593c4cbe1c96b3995727dc42f6aa103f4ff5afc, < 3658093df69849daf4f813a8f087f358e13be203Upgrade to: 3658093df69849daf4f813a8f087f358e13be203Affected: ≥ 4593c4cbe1c96b3995727dc42f6aa103f4ff5afc, < 73365b81630b57e1a1f9d50dc87281797855c2acUpgrade to: 73365b81630b57e1a1f9d50dc87281797855c2ac + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: only group hidden BSSes with beacon entries When a probe response for an unknown BSS comes in, __cfg80211_bss_update() looks for an existing entry with the same BSSID and a hidden (zero-length or NUL-filled) SSID, and if it finds one it groups them, using the beacon IEs from the existing entry. But that could find another entry without a beacon, if it was also from a probe response (with SSID), so there's a group without beacon elements. If a beacon with a hidden SSID for that BSSID arrives later, cfg80211_combine_bsses() goes looking for the probe response entries that belong to it - i.e. entries with the same BSSID and channel that have no beacon IEs - and finds those two. They are already grouped with each other, so it hits its WARN_ON_ONCE(bss->pub.hidden_beacon_bss) WARN_ON_ONCE(!list_empty(&bss->hidden_list)) which are there because an entry without beacon elements is not supposed to be part of a group yet. Only combine entries when a beacon was already received, ones that are kept separate will be combined when a beacon arrives.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/4cd6a518ce7527284bbc9baab5fa2453a7d477c2
- git.kernel.org/stable/c/74ed0d992f392c75e1969415527e06df3f7a4034
- git.kernel.org/stable/c/3658093df69849daf4f813a8f087f358e13be203
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI