# CVE-2026-90376: wifi: mt76: mt7996: fix MLD ID in MAC TXD and HIF TXP

> A flaw in the Linux kernel mt7996 WiFi driver causes a firmware busy loop and MCU timeout when handling frames for a third link in power saving mode.

- **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:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90376, GHSA-6ch6-r62g-8chc, UBUNTU-CVE-2026-90376

## What is CVE-2026-90376?

CVE-2026-90376 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: mt7996: fix MLD ID in MAC TXD and HIF TXP

Problem:
MCU command timeout while the firmware state is normal, and the
firmware keeps showing the error log "ERROR!! NO PAUSE...".

Root cause:
If the MLD_ID field in the TXD is neither the primary link id nor the
secondary link id, it may lead to a firmware busy loop when the third
link is in power saving mode.

Remap frames directed to a third link to the primary link wcid. Since
TX status events and txfree completions carry the wcid the firmware
saw, use the remapped wcid for packet id tracking and non-AQL packet
accounting as well, while the frame keeps its original link context
for addressing, band and OMAC selection.

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


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

Apply the vendor's patch.

## Is CVE-2026-90376 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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