PatchSiren cyber security CVE debrief
CVE-2026-53100 Linux CVE debrief
A deadlock vulnerability was found in the Linux kernel's WiFi mt76 module. The mt76_remain_on_channel() and mt76_roc_complete() functions call mt76_set_channel() while holding dev->mutex, leading to a deadlock. This issue has been resolved by using __mt76_set_channel() instead of mt76_set_channel() and adding cancel_delayed_work_sync() for mac_work. The affected product is the Linux kernel, specifically versions 6.14 to 6.18.33 and 6.19 to 7.0.10. The vulnerability class is a deadlock issue in the WiFi mt76 module. The likely operational impact is a denial-of-service (DoS) attack. The source-confidence limits are based on the provided CVE record and NVD entry.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- MEDIUM 5.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-24
- Original CVE updated
- 2026-07-21
- Advisory published
- 2026-06-24
- Advisory updated
- 2026-07-21
Who should care
Linux kernel maintainers, Linux distribution vendors, and users of Linux kernel versions 6.14 to 6.18.33 and 6.19 to 7.0.10 should be aware of this vulnerability and apply the provided patches. Affected operators include Linux kernel developers and maintainers. Affected platforms include Linux-based systems using the mt76 module. Vulnerability-management and security teams should review the provided patches and apply them to affected systems.
Technical summary
The Linux kernel's WiFi mt76 module is vulnerable to a deadlock issue. The mt76_remain_on_channel() and mt76_roc_complete() functions acquire dev->mutex and then call mt76_set_channel(), which also acquires dev->mutex, resulting in a deadlock. To fix this issue, the patch replaces mt76_set_channel() with __mt76_set_channel() and adds cancel_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remain_on_channel(). This fix is based on the official CVE record and NVD entry.
Defensive priority
Apply patches to prevent deadlock in mt76 module. This priority is based on the severity of the vulnerability and the potential impact on Linux-based systems.
Recommended defensive actions
- Apply patches from Linux kernel stable branches
- Inventory Linux kernel versions for potential exposure
- Monitor for potential exploit attempts
- Consider compensating controls for unpatched systems
- Review relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-06-24T17:17:24.257Z and last modified on 2026-07-21T18:21:01.780Z. The NVD entry is currently Analyzed. This information is based on the provided source corpus. Further verification is recommended to ensure accuracy.
Official resources
-
CVE-2026-53100 CVE record
CVE.org
-
CVE-2026-53100 NVD detail
NVD
-
Source item URL
nvd_modified
-
Mitigation or vendor reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
-
Mitigation or vendor reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
-
Mitigation or vendor reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-06-24T17:17:24.257Z and has not been modified since then. The NVD entry is currently Analyzed.