# CVE-2026-90365: wifi: mt76: cancel reset and rc work on device unregister

> A race condition in the mt76 Wi-Fi driver during device unregister can cause a kernel crash, requiring a patch to cancel pending work items.

- **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:** 21 Oct 2026
- **Also known as:** AZL-102425, BELL-CVE-2026-90365, DEBIAN-CVE-2026-90365, GHSA-mg5m-xfw2-63jw, UBUNTU-CVE-2026-90365

## What is CVE-2026-90365?

CVE-2026-90365 is a 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: cancel reset and rc work on device unregister

Both drivers cancelled dump_work on unregister but left reset_work and
rc_work to be flushed only by destroy_workqueue() in mt76_free_device(),
which runs after the hw is unregistered and the hardware stopped. A
reset_work that fires in that window calls ieee80211_restart_hw() and
re-arms mac_work on an unregistered hw, and rc_work touches station state
being torn down. Cancel both up front, alongside dump_work.

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


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

Apply the vendor's patch.

## Is CVE-2026-90365 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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