# CVE-2026-90375: wifi: mt76: fix non-AQL packet accounting for MLO stations

> A logic error in the mt76 Wi-Fi driver causes incorrect packet accounting, leading to permanent TX scheduler refusal and denial of service for MLO stations.

- **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:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102755, BELL-CVE-2026-90375, DEBIAN-CVE-2026-90375, GHSA-c2f5-4c4q-2g8j, UBUNTU-CVE-2026-90375

## What is CVE-2026-90375?

CVE-2026-90375 is a denial of service vulnerability in Linux, published on 17 Sep 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: mt76: fix non-AQL packet accounting for MLO stations

__mt76_tx_queue_skb() overrides the wcid passed by the driver with
sta->drv_priv, so the wcid might incorrectly be changed after TX,
causing wcid->non_aql_packets to be counted on the wrong wcid. For
example, on the AP side, if a station's setup link is the 5G link and
the station uses 2G to transmit a frame, the value of non_aql_packets
is increased on the 5G wcid but decreased on the 2G wcid. Once the
inflated counter exceeds MT_MAX_NON_AQL_PKT, the TX scheduler
permanently refuses to service the station.

Drop the reassignment and account on the wcid used for transmission.
This also records the actual wcid in the queue entry.

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


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

Apply the vendor's patch.

## Is CVE-2026-90375 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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