# CVE-2026-80936: wifi: mt76: mt7925: cancel mlo_pm_work on stop

> A race condition in the mt7925 WiFi driver causes a kernel warning and potential instability when the device is stopped during a delayed power-save work queue operation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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:** BELL-CVE-2026-80936, DEBIAN-CVE-2026-80936, GHSA-59xf-cqg5-4cpj, UBUNTU-CVE-2026-80936

## What is CVE-2026-80936?

CVE-2026-80936 is a high-severity 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: mt7925: cancel mlo_pm_work on stop

mt7925 queues mlo_pm_work with a 5 second delay during multi-link
power-save setup and never cancels it on the stop path. If the device is
torn down inside that window, the work outlives the teardown and its timer
fires afterwards, trying to queue onto the workqueue that is already gone:

  workqueue: cannot queue mt7925_mlo_pm_work [mt7925_common] on wq phy0
  WARNING: kernel/workqueue.c:2283 at __queue_work+0x59/0xa0, CPU#1: swapper/1/0
   call_timer_fn+0x2a/0x140
   __run_timers+0x203/0x330
   run_timer_softirq+0x86/0xf0

mt7921 already has its own stop callback, so add one for mt7925 that
cancels the work before calling mt792x_stop(). mt7925_ops backs both the
PCIe and USB drivers, so this covers both.

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


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

Apply the vendor's patch.

## Is CVE-2026-80936 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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