# CVE-2026-80938: wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex

> A race condition in the mt7615 Wi-Fi driver causes a deadlock during suspend, leading to a denial of service for local attackers.

- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100602, BELL-CVE-2026-80938, DEBIAN-CVE-2026-80938, GHSA-pv6c-cxx7-759w, UBUNTU-CVE-2026-80938

## What is CVE-2026-80938?

CVE-2026-80938 is a vulnerability in Linux, published on 11 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: mt7615: avoid waiting for mac work under the mt76 mutex

mt7615_suspend() acquired the mt76 mutex and then called
cancel_delayed_work_sync() on mac_work.  mt7615_mac_work() acquires the
same mutex via mt7615_mutex_acquire() at the top of the worker, so if
mac_work is already running and blocked on the mutex, the suspend path
deadlocks waiting for the work it holds the mutex against.

Flush scan_work and mac_work before taking the mutex, matching the
suspend paths in mt7921 and mt7925.  scan_work only takes the mt76
spinlock, but moving it keeps the sequence consistent.  This also keeps
mac_work from running over an already suspended HIF, which the previous
split (async cancel under the lock, sync cancel after release) would
have allowed.

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


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

Apply the vendor's patch.

## Is CVE-2026-80938 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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