# CVE-2026-98702: wifi: mac80211: reject invalid 320 MHz CSA bandwidth

> A remote attacker can crash the Linux kernel by sending a crafted Wi-Fi CSA frame if panic_on_warn is enabled.

- **Severity:** Not scored
- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98702, DEBIAN-CVE-2026-98702, GHSA-6466-2f74-2mgw, UBUNTU-CVE-2026-98702

## What is CVE-2026-98702?

CVE-2026-98702 is a denial of service vulnerability in Linux, published on 18 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: mac80211: reject invalid 320 MHz CSA bandwidth

The HT/VHT channel definition validator can receive a 320 MHz
bandwidth indication from a received CSA frame on a non-6 GHz link.
It warns for this unsupported width but continues with an uninitialized
vht_operation.chan_width, which is then read by
ieee80211_chandef_vht_oper(). With panic_on_warn enabled, this lets a
received frame panic the kernel.

Reject the channel definition before entering the VHT operation
conversion. This preserves the existing CSA fallback while avoiding
both the warning and the uninitialized read.

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


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

Apply the vendor's patch.

## Is CVE-2026-98702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98702 is a denial of service vulnerability in Linux, published on 18 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-98702 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-98702/ (Markdown: https://insights.sbomify.com/CVE-2026-98702/index.md)
```

## Sources

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

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