# CVE-2026-89523: wifi: mt76: mt7925: cancel pending mlo_pm_work

> A use-after-free vulnerability in the mt7925 Wi-Fi driver allows attackers to cause system crashes or potentially execute code during device reset or suspend operations.

- **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-89523, DEBIAN-CVE-2026-89523, GHSA-2cmm-rm3g-hc7x, UBUNTU-CVE-2026-89523

## What is CVE-2026-89523?

CVE-2026-89523 is a high-severity use after free 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 pending mlo_pm_work

If the device is reset, suspended or unregistered within that window,
the pending work can still run and access vif/bss data that may already
be freed, or send MCU commands while the firmware is not available.

Add cancel_delayed_work_sync(&dev->mlo_pm_work) in all relevant teardown
and suspend paths:

 - mt7925_mac_reset_work()        (chip reset recovery)
 - mt7925e_unregister_device()    (PCIe unbind)
 - mt7925_pci_suspend()           (PCIe bus suspend)
 - mt7925_suspend()               (mac80211 suspend)
 - mt7925u_suspend()              (USB bus / runtime suspend)

This ensures the work is stopped before the device state becomes
invalid.

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


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

Apply the vendor's patch.

## Is CVE-2026-89523 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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