wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12, 6.12.114, 6.18.33, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 45064d19fd3af6aeb0887b35b5564927980cf150 · fixed in 253cfc33d95ce4a30fd2eca0ff0138603c6c2fcc; From 45064d19fd3af6aeb0887b35b5564927980cf150 · fixed in 153bcba36c87a1ba555b57b6c49028d5812f895b; From 45064d19fd3af6aeb0887b35b5564927980cf150 · fixed in 2d8e0053bca29143ace51e08c980ff076844a4b0; From 45064d19fd3af6aeb0887b35b5564927980cf150 · fixed in dd08ca3f092f4185ece69ce2a835c23198b1628a; From 6.11.2 · fixed in 6.12
- Linux Linux
6.12
- KernelLinux
From 6.12.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10