# wifi: mt76: fix deadlock in remain-on-channel

CVE record · `CVE-2026-53100`

- **Identifiers:** `CVE-2026-53100`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Jun 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Jun 2026, 16:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `a8f424c1287cc79a06c21816658feea87dfcb83f to before 5fc8c5d45e44575dda9fcabdc2aac4ad97baf0cd` (git)
  - affected: `a8f424c1287cc79a06c21816658feea87dfcb83f to before 7a89c245d203aa0ed5ff2d68ac05b48b2ef9fa3f` (git)
  - affected: `a8f424c1287cc79a06c21816658feea87dfcb83f to before 6939b97ddad3cf3dfbb3b5a0a12ef79cb886747e` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.14`
  - unaffected: `before 6.14` (semver)
  - unaffected: `6.18.33 to 6.18.*, inclusive` (semver)
  - unaffected: `7.0.10 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's mt76 Wi-Fi driver has a deadlock in its remain-on-channel handling, affecting the 6.14 series, while earlier kernels are listed as unaffected. The source gives few details on what an attacker needs. Upgrade to 6.18.33 or later in the 6.18 series, 7.0.10 or later in the 7.0 series, or 7.1 or later.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Jun 2026, 16:30 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-53100)
- 24 Jun 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-53100)

## Sources

- [CVE List: CVE-2026-53100](https://www.cve.org/CVERecord?id=CVE-2026-53100)
- [NVD: CVE-2026-53100](https://nvd.nist.gov/vuln/detail/CVE-2026-53100)

### References from the CNA

- <https://git.kernel.org/stable/c/5fc8c5d45e44575dda9fcabdc2aac4ad97baf0cd>
- <https://git.kernel.org/stable/c/7a89c245d203aa0ed5ff2d68ac05b48b2ef9fa3f>
- <https://git.kernel.org/stable/c/6939b97ddad3cf3dfbb3b5a0a12ef79cb886747e>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-53100>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-53100/>. Everything for agents: <https://agentprime.io/llms.txt>.
