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

> A rogue AP can trigger a kernel warning and potential denial of service in the Linux Wi-Fi subsystem by manipulating BSS type entries during association updates.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106101, BELL-CVE-2026-98339, DEBIAN-CVE-2026-98339, GHSA-8rfq-q292-hgch, UBUNTU-CVE-2026-98339

## What is CVE-2026-98339?

CVE-2026-98339 is a high-severity denial of service vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98339?


## How do I fix CVE-2026-98339?

Apply the vendor's patch.

## Is CVE-2026-98339 being exploited?

There is no known exploitation of CVE-2026-98339 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98339 and fix it if it is affected.

What it is: CVE-2026-98339 is a high-severity denial of service vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98339 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98339/ (Markdown: https://insights.sbomify.com/CVE-2026-98339/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98339
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98339
- OSV: https://osv.dev/vulnerability/CVE-2026-98339

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98339/
Summaries are generated and may contain mistakes; the official description above is the record.