PatchSiren

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.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-53103 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-53103

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-53103 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-53103

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Mitigation or vendor reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/153bcba36c87a1ba555b57b6c49028d5812f895b

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Mitigation or vendor reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/2d8e0053bca29143ace51e08c980ff076844a4b0

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

  • Mitigation or vendor reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/dd08ca3f092f4185ece69ce2a835c23198b1628a

    416baaa9-dc9f-4396-8d5f-8c081fb06d67 - Patch

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.