dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53104

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 memory leak destroying device All MT76 rx queues have an associated page_pool even if the queue is not associated to a NAPI (e.g. WED RRO queues with WED enabled). Destroy the page_pool running mt76_dma_cleanup routine during module unload. Moreover returns pages to the page pool if WED is not enabled for WED RRO queues.

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 memory leak exists in the Linux kernel's mt76 wifi driver where page_pool structures associated with MT76 rx queues are not properly destroyed during module unload. The page_pool exists even for queues not associated with a NAPI (such as WED RRO queues), and these must be cleaned up in mt76_dma_cleanup. Additionally, pages must be returned to the page_pool when WED is not enabled for WED RRO queues.

MitigationThe fix requires modifying mt76_dma_cleanup to destroy page_pool structures during module unload and ensuring pages are returned to the page_pool for WED RRO queues when WED is disabled. This is a kernel driver-level fix requiring code changes to the mt76 driver.

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.8, < 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 and compare against the affected ranges: >= 6.8 and < 6.18.33, or >= 6.9 and < 7.0.10
    Affected if The kernel version falls within either of the two affected ranges (>= 6.8, < 6.18.33 or >= 6.19, < 7.0.10)
  2. Verify mt76 driver is loaded
    Run 'lsmod | grep mt76' to check if any mt76 driver modules are currently loaded in memory
    Affected if Any mt76 driver module (such as mt76x2u, mt76x2e, mt7615e, mt7921e, etc.) is loaded
  3. Check for WED enablement
    Check system logs or configuration for Wireless Endpoint Dispatcher (WED) being enabled, typically found in boot parameters or device tree configurations for the wireless interface
    Affected if WED is enabled on the system
  4. Monitor for page_pool memory leaks
    Check /sys/kernel/debug/page_pool/ (if available) for page_pool statistics, or use 'cat /proc/meminfo' and monitor for unusual memory growth over time while the mt76 driver is loaded and unloaded repeatedly
    Affected if Repeated module reload cycles show increasing unreclaimed memory allocations associated with page_pool structures

The system is affected if it runs a kernel in the vulnerable version range, has the mt76 WiFi driver loaded, and has WED enabled, leading to unreleased page_pool memory during driver unload.

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

The fix requires modifying mt76_dma_cleanup to destroy page_pool structures during module unload and ensuring pages are returned to the page_pool for WED RRO queues when WED is disabled. This is a kernel driver-level fix requiring code changes to the mt76 driver.

Recommended fix High confidence

6.18.33 or 7.0.10 (depending on your current major version)

  1. Upgrade Linux kernel to version 6.18.33 or later if currently running version 6.8 or later but earlier than 6.18.33
  2. Alternatively, upgrade to version 7.0.10 or later if currently running version 6.19 or later but earlier than 7.0.10
  3. After kernel upgrade, reboot the system to load the fixed kernel
  4. Verify the fix is applied by checking that mt76 module properly cleans up page_pool during unload (no memory leak in dmesg after module operations)
Caveat Kernel upgrades may introduce compatibility changes with third-party modules or drivers; ensure dependent modules are compatible with the target version

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

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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