wifi: mt76: fix deadlock in remain-on-channel
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.337.0.107.1In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: fix deadlock in remain-on-channel
mt76_remain_on_channel() and mt76_roc_complete() call mt76_set_channel() while already holding dev->mutex. Since mt76_set_channel() also acquires dev->mutex, this results in a deadlock.
Use __mt76_set_channel() instead of mt76_set_channel(). Add cancel_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remain_on_channel() to prevent a secondary deadlock with the mac_work workqueue.
From the CVE record · Linux
The Linux kernel’s mt76 Wi-Fi driver can deadlock when remain-on-channel operations try to acquire a mutex that is already held. The input does not specify how an attacker could trigger the issue or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with the mt76 Wi-Fi driver should check their versions; affected versions are not specified.