dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53101

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.12.95 / 6.18.33 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: mt7921: fix potential deadlock in mt7921_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() -> mt7921_mac_sta_remove() -> mt7921_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 mt7921 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. If the caller already owns the same mutex during station removal (via mt76_sta_state() -> mt76_sta_remove() -> mt7921_mac_sta_remove() -> mt7921_roc_abort_sync()), both sides block indefinitely.

MitigationApply the kernel patch that restructures mutex handling in mt7921_roc_abort_sync() to avoid acquiring the mutex when cancel_work_sync() is called, preventing the circular wait condition while preserving exactly-once work semantics.

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.9, < 6.12.95>= 6.13, < 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. Check if mt7921 WiFi driver is loaded
    Run 'lsmod | grep mt7921' or check 'lspci -k' for Network controller using mt7921 driver
    Affected if No mt7921 driver loaded means not affected
  2. Identify kernel version
    Run 'uname -r' to get the running kernel version
    Affected if Kernel version falls outside these ranges: >=6.9 and <6.12.95, >=6.13 and <6.18.33, >=6.19 and <7.0.10 - if outside, not affected
  3. Verify driver source contains vulnerable function
    Check if /lib/modules/$(uname -r)/kernel/drivers/net/wireless/mediatek/mt7921/ exists, or inspect driver source for mt7921_roc_abort_sync function
    Affected if Driver module exists with the vulnerable function code present in affected kernel versions
  4. Confirm WiFi hardware is active
    Run 'iw dev' or 'ip link show' to list wireless interfaces, then 'ethtool -i <interface>' to confirm mt7921 driver association
    Affected if No active mt7921-managed interface means the deadlock scenario cannot be triggered

System is affected only if mt7921 WiFi driver is loaded, the kernel version is within the affected ranges, and the vulnerable mt7921_roc_abort_sync function exists in the driver code.

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.12.95 / 6.18.33 / 7.0.10 or later
Fixed in 6.12.956.18.337.0.10
Interim mitigation

Apply the kernel patch that restructures mutex handling in mt7921_roc_abort_sync() to avoid acquiring the mutex when cancel_work_sync() is called, preventing the circular wait condition while preserving exactly-once work semantics.

Recommended fix High confidence

Linux Kernel 6.12.95+, 6.18.33+, or 7.0.10+ depending on which major branch you are on

  1. Identify the current running kernel version using `uname -r`
  2. Determine which version range your current kernel falls into (>= 6.9, < 6.12.95; >= 6.13, < 6.18.33; or >= 6.19, < 7.0.10)
  3. Upgrade the Linux kernel to a version that includes the fix: 6.12.95 or later for the 6.12.y branch, 6.18.33 or later for the 6.13-6.18 branch, or 7.0.10 or later for the 6.19+ branch
  4. Use your distribution's package manager to install the updated kernel (e.g., `apt update && apt install linux-image-<version>` for Debian/Ubuntu, or `dnf update kernel` for Fedora/RHEL)
  5. Reboot the system to load the fixed kernel
  6. Verify the new kernel version is running with `uname -r`
Caveat Kernel upgrades may require rebooting services; ensure compatibility with local system configurations and installed modules before upgrading

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53101 — 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-53101 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