Skip to main content
VulnerabilityPublished Updated

CVE-2026-53103: Linux kernel · wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in dd08ca3f092f4185ece69ce2a835c23198b1628a : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in dd08ca3f092f4185ece69ce2a835c23198b1628a, 253cfc33d95ce4a30fd2eca0ff0138603c6c2fcc, 153bcba36c87a1ba555b57b6c49028d5812f895b +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.11.2 <6.12
Fixed in
  • dd08ca3f092f4185ece69ce2a835c23198b1628a
  • 253cfc33d95ce4a30fd2eca0ff0138603c6c2fcc
  • 153bcba36c87a1ba555b57b6c49028d5812f895b
  • 6.12
  • 2d8e0053bca29143ace51e08c980ff076844a4b0
LinuxLinuxAffected
  • =6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix potential deadlock in mt7925_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() -> mt7925_mac_sta_remove_link() -> mt7925_mac_link_sta_remove() -> mt7925_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

Community reviews

Loading reviews…