[CVE-2026-53104][LOW] wifi: mt76: Fix memory leak destroying device [ Upstream

[CVE-2026-53104][LOW] wifi: mt76: Fix memory leak destroying device [ Upstream

[AL-KERNEL]

CVE: CVE-2026-53104
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: wifi: mt76: Fix memory leak destroying device [ Upstream
Commit: dcbc13d19bef3326c72f324b10f5a3e5fc4d71de
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dcbc13d19bef3326c72f324b10f5a3e5fc4d71de
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53104
Analysis date: Fri, 26 Jun 2026 11:55:04 -0400
ActionableScore: 2
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
MT76 WED RRO RX queue cleanup could leak page_pool resources during device destruction or module unload, requiring local device management privileges in typical deployments and causing only potential denial of service through resource exhaustion.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53104 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53104

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-53104	LOW	CHECK	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.5';DESCR 'mt76 device cleanup can leak page_pool resources because WED RRO RX queues were skipped during DMA cleanup even though these queues still have an associated page_pool. The issue is reached during device destruction or module unload and can accumulate memory over repeated unload or recovery cycles. For the CVSS the PR:L is used in the paranoid score only for environments where a local actor has delegated device management or network administration capabilities that can repeatedly reset or destroy the device. The issue is not network reachable through WiFi traffic alone. Impact is denial of service via resource exhaustion only and there is no indication of memory corruption or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 1) 	MAYBE	REMOTE SIMPLEFIX LEAK NETWORK HARDWARE MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

Conservative signals:

* Resource leak only: 0. The patch fixes a page_pool cleanup omission, not UAF, double free, OOB write, or object confusion.
* Requires admin/root/CAP level device control: -2. The affected path is device destruction, module unload, or similar driver cleanup lifecycle.
* Availability impact realistic: +1. Repeated cleanup failures may leak memory and eventually contribute to resource exhaustion.
* Rare/configuration dependent hardware path: -1. This requires MT76 hardware with WED RRO related queues and the affected driver configuration.
* Score clamped to 0 for practical triage.

Paranoid signals:

* Local delegated trigger: +1. If an untrusted local actor has delegated device management or network administration capability, repeated reset or recovery cycles may be possible.
* Availability impact realistic: +1. Sustained repeated cycles could cause memory pressure or resource exhaustion.
* No memory corruption signal is applied. The patch shows missing cleanup of page_pool backed resources, not a corruption primitive.
* No privilege escalation signal is applied. There is no reclaim, stale pointer reuse, arbitrary write, or shared page ownership violation.

## 3. Reachability analysis

The bug is reached during mt76 device cleanup, module unload, or device destruction and not through ordinary WiFi packet reception alone. In typical deployments this requires administrative control over the driver or device lifecycle, so the conservative interpretation treats it as requiring high privileges. Namespace or container delegation could lower this to a local privileged container or service account scenario if device reset or network device management is exposed. The affected configuration is hardware and driver specific, mainly MT76 with WED RRO support.

## 4. Severity interpretation

This behaves like a Low-like or ordinary Moderate resource leak, not an Important kernel vulnerability. The realistic impact is memory/resource leakage across repeated cleanup or recovery cycles. The patch does not support memory corruption, privilege escalation, information disclosure, or a network reachable trigger. The paranoid score only accounts for delegated local device control and sustained resource exhaustion.

## 5. One-sentence report phrase

MT76 WED RRO RX queue cleanup could leak page_pool resources during device destruction or module unload, requiring local device management privileges in typical deployments and causing only potential denial of service through resource exhaustion.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be auto-closed for urgent security triage because it is a cleanup-time resource leak with no supported memory corruption primitive, no direct remote reachability, and no plausible privilege escalation path from the patch context.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: wifi: mt76: Fix memory leak destroying device [ Upstream
Commit: dcbc13d19bef3326c72f324b10f5a3e5fc4d71de
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dcbc13d19bef3326c72f324b10f5a3e5fc4d71de

Changed files:
  drivers/net/wireless/mediatek/mt76/dma.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=dcbc13d19bef3326c72f324b10f5a3e5fc4d71de

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-53104 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53104

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 5.5

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 0
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).