# CVE-2026-98346: wifi: cfg80211: don't get the radio mask for netdev-less wdevs

> A null pointer dereference in the Linux kernel WiFi subsystem allows local attackers to cause a system crash by triggering a specific code path with a netdev-less wireless device.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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:** BELL-CVE-2026-98346, DEBIAN-CVE-2026-98346, GHSA-36pm-6m6w-jv8x, UBUNTU-CVE-2026-98346

## What is CVE-2026-98346?

CVE-2026-98346 is a 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 get the radio mask for netdev-less wdevs

cfg80211_calculate_bi_data() calls rdev_get_radio_mask() with
wdev->netdev, which can be NULL and then crashes in mac80211.

To avoid that, invert the order of checks since wdev->netdev
is always valid for beaconing interfaces.

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


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

Apply the vendor's patch.

## Is CVE-2026-98346 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98346 is a 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-98346 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-98346/ (Markdown: https://insights.sbomify.com/CVE-2026-98346/index.md)
```

## Sources

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

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