# CVE-2026-90367: wifi: mt76: mt7996: hold dev->mt76.mutex while disabling tx worker in SER

> A race condition in the mt7996 WiFi driver can corrupt DMA descriptors during reset, potentially causing system instability or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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-102164, BELL-CVE-2026-90367, DEBIAN-CVE-2026-90367, GHSA-rjqr-mg4v-422g, UBUNTU-CVE-2026-90367

## What is CVE-2026-90367?

CVE-2026-90367 is a high-severity 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: hold dev->mt76.mutex while disabling tx worker in SER

mt7996_mac_reset_work() parked the tx worker and disabled the RX/TX NAPIs
before taking dev->mt76.mutex. mt76_worker_disable()/_enable() are plain
kthread park/unpark, not refcounted, and __mt76_set_channel() toggles the
same worker and the MT76_RESET bit under the mutex. An L1 SER racing a
channel switch could therefore have the worker unparked and MT76_RESET
cleared while the reset path resets the DMA rings, corrupting descriptors
or tokens. Take the mutex before disabling the worker, as mt7915 does.

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


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

Apply the vendor's patch.

## Is CVE-2026-90367 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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