wifi: cfg80211: don't filter by BSS type when removing stale entries
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0aa44982125c86b47961be5ac1c82eddab8080f3, 1380ee3a202dbb9f8e8b3c3b87eb410450d57799, 64e23a36d8f04811372365b44cfca325f8e0f4bb; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 0aa44982125c86b47961be5ac1c82eddab8080f3, 1380ee3a202dbb9f8e8b3c3b87eb410450d57799, 64e23a36d8f04811372365b44cfca325f8e0f4bb; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.4affected
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before 6ef87a853327434ae1cd9c5a2c27a557fb4047fcaffected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before 1380ee3a202dbb9f8e8b3c3b87eb410450d57799affected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before fb445ec7480da5d2b82bf681e3b4313603722729affected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before 65fdb973bd905bc3f5cb045a04c1828f2d2a7e24affected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before 64e23a36d8f04811372365b44cfca325f8e0f4bbaffected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before 6d2fd26185678038ef2ea11dd4d2e6eccbf2dd25affected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before 0aa44982125c86b47961be5ac1c82eddab8080f3affected · git
- 0afd425b1b64251f19b5d8d8b49bf56fefbc643f and later · before b377e1000d963e7182a987082b4b06580bd7ac84affected · git
- before 5.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98337Oct 6, 2026 · wifi: mac80211: don't start a ROC while scanning0Monitor
- ← EarlierCVE-2026-98338Oct 6, 2026 · wifi: cfg80211: ibss: ref BSS entry for joined event0Monitor
- Later →CVE-2026-98340Oct 6, 2026 · wifi: cfg80211: only group hidden BSSes with beacon entries0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0aa44982125c86b47961be5ac1c82eddab8080f3 | Vendor (CNA) |
| Linux Linux | 1380ee3a202dbb9f8e8b3c3b87eb410450d57799 | Vendor (CNA) |
| Linux Linux | 64e23a36d8f04811372365b44cfca325f8e0f4bb | Vendor (CNA) |
| Linux Linux | 65fdb973bd905bc3f5cb045a04c1828f2d2a7e24 | Vendor (CNA) |
| Linux Linux | 6d2fd26185678038ef2ea11dd4d2e6eccbf2dd25 | Vendor (CNA) |
| Linux Linux | 6ef87a853327434ae1cd9c5a2c27a557fb4047fc | Vendor (CNA) |
| Linux Linux | b377e1000d963e7182a987082b4b06580bd7ac84 | Vendor (CNA) |
| Linux Linux | fb445ec7480da5d2b82bf681e3b4313603722729 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 24, 2026+18 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 8.8
- Severity— → high
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1380ee3a202dbb9f8e8b3c3b87eb410450d57799
- git.kernel.org/stable/c/64e23a36d8f04811372365b44cfca325f8e0f4bb
- git.kernel.org/stable/c/65fdb973bd905bc3f5cb045a04c1828f2d2a7e24
- git.kernel.org/stable/c/6d2fd26185678038ef2ea11dd4d2e6eccbf2dd25
- git.kernel.org/stable/c/6ef87a853327434ae1cd9c5a2c27a557fb4047fc
- git.kernel.org/stable/c/b377e1000d963e7182a987082b4b06580bd7ac84
- git.kernel.org/stable/c/fb445ec7480da5d2b82bf681e3b4313603722729
Vendor advisories and official records. Exploit/PoC links are deliberately left out.