CVE-2026-53101: Linux kernel · wifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d5059e52fd8bc624ec4255c9fa01a266513d126b : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in d5059e52fd8bc624ec4255c9fa01a266513d126b, b4faaa617af3f4173e64169b0ec1af8f9c5bca10, 35180c772f5e11e2fa4d80d3dfd50906cb6d9646 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Linux kernel to d5059e52fd8bc624ec4255c9fa01a266513d126b, b4faaa617af3f4173e64169b0ec1af8f9c5bca10, 35180c772f5e11e2fa4d80d3dfd50906cb6d9646 or 91e77840bf13de3add125060cf8b32ca24a52c8c.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921: fix potential deadlock in mt7921_roc_abort_sync roc_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex, while cancel_work_sync() waits for roc_work() to finish. If the caller already owns the same mutex, both sides block and no progress is possible. This deadlock can occur during station removal when mt76_sta_state() -> mt76_sta_remove() -> mt7921_mac_sta_remove() -> mt7921_roc_abort_sync() invokes cancel_work_sync() while roc_work() is still running and holding dev->mt76.mutex. This avoids the mutex deadlock and preserves exactly-once work ownership.
References
- git.kernel.org/stable/c/b4faaa617af3f4173e64169b0ec1af8f9c5bca10 (opens in a new tab)
- git.kernel.org/stable/c/35180c772f5e11e2fa4d80d3dfd50906cb6d9646 (opens in a new tab)
- git.kernel.org/stable/c/91e77840bf13de3add125060cf8b32ca24a52c8c (opens in a new tab)
- git.kernel.org/stable/c/d5059e52fd8bc624ec4255c9fa01a266513d126b (opens in a new tab)