PatchSiren cyber security CVE debrief
CVE-2026-53103 Linux CVE debrief
A medium-severity vulnerability, CVE-2026-53103, was found in the Linux kernel. This issue could lead to a potential deadlock in the mt7925_roc_abort_sync function. The vulnerability arises from a deadlock between roc_abort_sync() and roc_work(). The roc_work() function holds the dev->mt76.mutex, while roc_abort_sync() waits for roc_work() to finish using cancel_work_sync(). 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.
- 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.11.2 to 6.18.33 or 6.19 to 7.0.10 should be aware of this vulnerability and take necessary actions to mitigate the risk.
Technical summary
The CVE-2026-53103 vulnerability is caused by a potential deadlock in the mt7925_roc_abort_sync function of the Linux kernel. The deadlock occurs between roc_abort_sync() and roc_work(). The roc_work() function holds the dev->mt76.mutex, while roc_abort_sync() waits for roc_work() to finish. If the caller already owns the same mutex, both sides block, and no progress is possible. This issue can happen during station removal. The vulnerability has been resolved by avoiding the mutex deadlock and preserving exactly-once work ownership.
Defensive priority
Medium priority should be given to patching this vulnerability, as it could potentially lead to a denial-of-service (DoS) attack.
Recommended defensive actions
- Apply the official patches provided by the Linux kernel maintainers.
- Update Linux kernel to a version outside the vulnerable range (before 6.11.2 or after 6.18.33, or before 6.19 or after 7.0.10).
- Monitor system logs for potential deadlock occurrences.
- Implement compensating controls, such as limiting access to the affected systems.
- Review system configurations to ensure they are not vulnerable.
- Perform regular security audits to identify potential vulnerabilities.
- Track and verify patch deployments for CVE-2026-53103.
Evidence notes
The CVE record was published on 2026-06-24T17:17:24.567Z and was last modified on 2026-07-21T18:20:17.650Z. The NVD entry is currently Analyzed. The vulnerability has a CVSS score of 5.5 and a severity of MEDIUM.
Official resources
-
CVE-2026-53103 CVE record
CVE.org
-
CVE-2026-53103 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.567Z and has not been modified since then. The NVD entry is currently Analyzed.