Bug 2492445 (CVE-2026-53100)

Summary:	CVE-2026-53100 kernel: wifi: mt76: fix deadlock in remain-on-channel
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	rhel-process-autobot, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A flaw was found in the Linux kernel's mt76 wireless driver. This vulnerability occurs in the `remain-on-channel` functionality, where the `mt76_remain_on_channel()` and `mt76_roc_complete()` functions attempt to acquire a mutex that is already held. This improper handling of the device mutex can lead to a system deadlock, causing the system to become unresponsive. Additionally, a secondary deadlock can occur with the `mac_work` workqueue.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-06-24 18:12:27 UTC

In 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.

Comment 1 Mauro Matteo Cascella 2026-06-24 19:22:32 UTC

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062411-CVE-2026-53100-835e@gregkh/T