# CVE-2026-98958: wifi: mt76: account non-AQL frames per peer rather than per link


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-98958, DEBIAN-CVE-2026-98958, GHSA-ffj9-hv8w-32hf, UBUNTU-CVE-2026-98958

## What is CVE-2026-98958?

CVE-2026-98958 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: mt76: account non-AQL frames per peer rather than per link

The driver increments wcid->non_aql_packets when a frame goes to the
hardware queue. The completion path decrements the counter again.

For an MLO peer, the hardware reports the completion on the link that it
used for the transmission. This link can differ from the link that the
driver queued the frame on. In that case, the increment and the
decrement go to different link wcids, and the count drifts upwards until
it blocks the station.

Keep the count on the wcid of the primary link, like the other peer-wide
state.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98958 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98958 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-98958/ (Markdown: https://insights.sbomify.com/CVE-2026-98958/index.md)
```

## Sources

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

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