dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53103

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.18.33 / 7.0.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync roc_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex, while cancel_work_sync() waits for roc_work() to finish. 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. This avoids the mutex deadlock and preserves exactly-once work ownership.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A deadlock vulnerability exists in the Linux kernel's mt7925 WiFi driver where roc_abort_sync() can deadlock with roc_work(). roc_work() holds dev->mt76.mutex while cancel_work_sync() waits for roc_work() to finish. During station removal via mt76_sta_state() -> mt7925_roc_abort_sync(), if the caller already owns the same mutex, both sides block indefinitely.

MitigationUpdate the Linux kernel to a version containing the fix for this mutex deadlock, or apply the vendor-specific patch that resolves the roc_abort_sync/roc_work mutex contention issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.11.2, < 6.18.33>= 6.19, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify mt7925 WiFi hardware in system
    Run 'lspci | grep -i mt7925' or 'lspci | grep -i mediatek' to check for MediaTek mt7925 wireless devices
    Affected if No mt7925 device found - not affected by this specific driver vulnerability
  2. Check installed kernel version
    Run 'uname -r' to get the kernel version, then compare against >= 6.11.2 and < 6.18.33, or >= 6.19 and < 7.0.10
    Affected if Kernel version falls within the affected ranges listed in the CVE
  3. Verify mt7925 driver is loaded
    Run 'lsmod | grep mt7925' or check 'ls /sys/bus/pci/drivers/mt7925e/' to confirm the driver module is active
    Affected if Driver not loaded - the vulnerable code path cannot be triggered
  4. Check for station removal activity
    The vulnerability triggers during station removal via mt76_sta_remove() call chain. Monitor for WiFi client disconnections or access point unconfiguration events
    Affected if No station removal events occur - the deadlock condition is not triggered even with vulnerable code present
  5. Inspect driver source for vulnerable code pattern
    If driver source is available, verify roc_abort_sync() calls cancel_work_sync() while dev->mt76.mutex may be held (lines in mt7925/mcu.c or related mt76 driver files)
    Affected if The specific mutex-held-during-cancel_work_sync pattern exists in the loaded driver version

System is affected if it runs a vulnerable kernel version (within the listed ranges), has mt7925 WiFi hardware, loads the mt7925 driver, and performs station removal operations that trigger the mutex deadlock condition.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.33 / 7.0.10 or later
Fixed in 6.18.337.0.10
Interim mitigation

Update the Linux kernel to a version containing the fix for this mutex deadlock, or apply the vendor-specific patch that resolves the roc_abort_sync/roc_work mutex contention issue.

Recommended fix High confidence

Linux Kernel 6.18.33 or 7.0.10 (or any later stable release)

  1. Identify the current running kernel version using `uname -r`
  2. Check if the version falls within affected ranges: >= 6.11.2, < 6.18.33 or >= 6.19, < 7.0.10
  3. Plan maintenance window for kernel upgrade as it requires system reboot
  4. Schedule and perform kernel upgrade to a fixed version
  5. Reboot the system to load the new kernel
  6. Verify the new kernel version is running post-reboot with `uname -r`
  7. Confirm the fix is applied by checking that the mt7925 driver no longer has the deadlock issue
Caveat Kernel upgrade requires system reboot and may have compatibility implications with existing system configurations or third-party modules; ensure backup and test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53103 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data