CVE-2026-98339
wifi: cfg80211: don't filter by BSS type when removing stale entries
No known exploitation. EPSS puts it in the 19th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, < 6ef87a853327434ae1cd9c5a2c27a557fb4047fcUpgrade to: 6ef87a853327434ae1cd9c5a2c27a557fb4047fcAffected: ≥ 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, < 1380ee3a202dbb9f8e8b3c3b87eb410450d57799Upgrade to: 1380ee3a202dbb9f8e8b3c3b87eb410450d57799Affected: ≥ 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, < fb445ec7480da5d2b82bf681e3b4313603722729Upgrade to: fb445ec7480da5d2b82bf681e3b4313603722729Affected: ≥ 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, < 65fdb973bd905bc3f5cb045a04c1828f2d2a7e24Upgrade to: 65fdb973bd905bc3f5cb045a04c1828f2d2a7e24 + 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: don't filter by BSS type when removing stale entries When an assoc AP switches to a channel that already has a BSS entry, cfg80211_update_assoc_bss_entry() removes that entry before rehashing the real one, since the two would otherwise collide in the BSS rbtree. The lookup for that entry also required it to match the connection's BSS type, so an entry advertising e.g. the IBSS capability bit was left in place, and the following cfg80211_rehash_bss() then ran into it: WARN_ON(!cmp) Changing the type shouldn't really happen, but can be triggered by a rogue AP/device, so drop the check and remove any entries matching the comparison.
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.3% chance of exploitation activity in the next 30 days, which ranks it in the 19th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
3 events over 1 day, from the signal feeds we watch.
- Record updated
- Publishedrecord updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Scored 8.8 by NVD.
How it is reached
- Attack Vector AdjacentRequires access to the local network (e.g. same Wi-Fi, Bluetooth)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Sources
References in the record
- git.kernel.org/stable/c/0aa44982125c86b47961be5ac1c82eddab8080f3
- git.kernel.org/stable/c/1380ee3a202dbb9f8e8b3c3b87eb410450d57799
- git.kernel.org/stable/c/64e23a36d8f04811372365b44cfca325f8e0f4bb
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