# CVE-2026-98329: wifi: mac80211: don't allow injecting frames wider than the chanctx

> A local attacker with monitor interface access can cause a kernel warning or potential denial of service by injecting Wi-Fi frames with invalid bandwidth parameters.

- **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:** AZL-106415, BELL-CVE-2026-98329, DEBIAN-CVE-2026-98329, GHSA-5g9w-qmxp-3m5f, UBUNTU-CVE-2026-98329

## What is CVE-2026-98329?

CVE-2026-98329 is a 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: mac80211: don't allow injecting frames wider than the chanctx

Frames injected on a monitor interface can carry a radiotap
field requesting a bandwidth, which mac80211 passes down to
the driver regardless of the the actual operational bandwidth.

If the bandwidth requested is too wide, that triggers a warning
in hwsim:

  WARN_ON(hwsim_get_chanwidth(bw) > hwsim_get_chanwidth(confbw))

Drop such frames entirely instead since they cannot be sent.

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


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

Apply the vendor's patch.

## Is CVE-2026-98329 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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