dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53100

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: fix deadlock in remain-on-channel mt76_remain_on_channel() and mt76_roc_complete() call mt76_set_channel() while already holding dev->mutex. Since mt76_set_channel() also acquires dev->mutex, this results in a deadlock. Use __mt76_set_channel() instead of mt76_set_channel(). Add cancel_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remain_on_channel() to prevent a secondary deadlock with the mac_work workqueue.

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 mt76 WiFi driver where mt76_remain_on_channel() and mt76_roc_complete() call mt76_set_channel() while already holding dev->mutex. Since mt76_set_channel() also acquires dev->mutex, this creates a classic deadlock. Additionally, a secondary deadlock risk exists with the mac_work workqueue.

MitigationReplace mt76_set_channel() with __mt76_set_channel() (non-locking variant) and add cancel_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remain_on_channel() to prevent the secondary deadlock.

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.14, < 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 kernel version
    Run `uname -r` to get the running kernel version
    Affected if The kernel version falls within >= 6.14 and < 6.18.33, or >= 6.19 and < 7.0.10
  2. Identify mt76 driver presence
    Run `lsmod | grep mt76` or check `ls /sys/module/ | grep mt76` to see if the mt76 kernel module is loaded
    Affected if The mt76 module is loaded in memory
  3. Check for mt76 wireless interfaces
    Run `iw dev` or `ip link show` to list wireless interfaces, then check their driver via `ethtool -i <interface>` or `cat /sys/class/net/<interface>/device/driver`
    Affected if Wireless interfaces managed by the mt76 driver exist on the system
  4. Verify remain-on-channel capability
    Attempt `iw dev <interface> interface info` to check if the interface supports monitor mode or remain-on-channel operations
    Affected if The mt76 interface supports remain-on-channel or monitor mode operations

You are affected if your system runs a vulnerable kernel version (>= 6.14 and < 6.18.33, or >= 6.19 and < 7.0.10) AND has mt76 driver loaded with active wireless interfaces that can trigger remain-on-channel operations.

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

Replace mt76_set_channel() with __mt76_set_channel() (non-locking variant) and add cancel_delayed_work_sync() for mac_work before acquiring the mutex in mt76_remain_on_channel() to prevent the secondary deadlock.

Recommended fix High confidence

6.18.33 or 7.0.10 (whichever is applicable to your major version branch)

  1. Identify the currently running Linux kernel version using `uname -r`
  2. If running kernel >= 6.14 and < 6.18.33, upgrade to kernel version 6.18.33 or later
  3. If running kernel >= 6.19 and < 7.0.10, upgrade to kernel version 7.0.10 or later
  4. Alternatively, if the distribution provides a patched kernel, apply the patch that replaces `mt76_set_channel()` with `__mt76_set_channel()` in mt76_remain_on_channel() and adds `cancel_delayed_work_sync(&dev->mac_work)` before mutex acquisition
  5. Reboot into the updated kernel and verify the wireless driver loads without deadlock errors
Caveat Standard kernel upgrade risks apply - ensure driver compatibility with the new kernel version

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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