[CVE-2026-72216][LOW] remoteproc: qcom: Fix leak when custom dump_segments addition fails

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-72216
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: remoteproc: qcom: Fix leak when custom dump_segments addition fails
Commit: 65104d6eb43f066dcf73ca9ade6478824b17d867
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=65104d6eb43f066dcf73ca9ade6478824b17d867
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72216
Analysis date: Sat, 15 Aug 2026 16:52:04 -0400
ActionableScore: 1
ActionableScore lower bound: 0
Actionable bucket: Ordinary Moderate / Low-like auto-close candidate
Manual review required: NO

Summary:
A privileged Qualcomm remoteproc minidump error path can leak allocated region name strings when custom coredump segment creation fails, potentially causing minor resource exhaustion only after repeated failures.

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

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

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-72216	LOW	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;CWE-703;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'A memory leak in the Qualcomm remoteproc minidump path can occur when qcom_add_minidump_segments allocates a region name but rproc_coredump_add_custom_segment fails before the region is added to dump_segments. The leaked name is then not tracked by qcom_minidump_cleanup and can accumulate only if the failing path is reached repeatedly. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over remoteproc operation or a privileged component that can induce repeated remote processor crash or dump collection paths. The issue is not network reachable and does not provide a memory corruption primitive. Impact is denial of service through resource exhaustion only, with low practical severity unless failures can be repeated many times on affected Qualcomm systems.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like auto-close candidate (with actual score 1)	YES	NOMEMCHK LEAK UAF DEBUGFS LINUS MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

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

ActionableScore=1
ActionableScoreLower=0

## 1. ActionableScore

* Conservative score: 0
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate / Low-like auto-close candidate**

## 2. Signal breakdown

Triggered signals:

* Firmware-mediated external influence: +1 paranoid only. The minidump region data comes from Qualcomm remoteproc/minidump context, but the actual leak requires the custom segment addition failure path, not merely firmware input.
* Availability impact realistic: +1 paranoid only. Repeated leaks could theoretically cause resource exhaustion, but each leak is small and depends on repeated failures.
* Requires admin/root/CAP_* in typical deployments: -2. Reliable triggering normally requires privileged remoteproc control, device crash handling, or platform management access.
* Rare AND difficult-to-reach subsystem/configuration: -1. This is Qualcomm remoteproc minidump handling, not a broad default user-facing kernel path.

Not triggered:

* No generic memory corruption. This is a lost allocation, not UAF, double free, OOB write, type confusion, or refcount corruption.
* No privilege escalation plausible. No reclaim, overwrite, stale callback, controlled object reuse, or arbitrary write is shown.
* No confidentiality or integrity impact. The patch only fixes ownership of an allocated name string on an error path.
* No reliable strong DoS in the conservative score. Practical DoS requires repeated successful triggering of the same failure path.

## 3. Reachability analysis

The bug is local and privileged in realistic deployments. A normal unprivileged user is not expected to control Qualcomm remoteproc minidump setup or reliably force repeated qcom_add_minidump_segments failure cycles.

Namespaces and containers do not meaningfully lower the privilege requirement unless a product explicitly delegates remoteproc control to a less privileged service or container, which would be unusual.

The affected path is hardware and platform specific. It requires Qualcomm remoteproc minidump support and an error while adding a custom coredump segment. This is not network reachable.

Call-site confidence: medium. The patch shows the allocation, failure path, and cleanup issue directly, but not all external trigger paths for repeated minidump collection.

## 4. Severity interpretation

This behaves like a Low-like or ordinary Moderate resource leak, not an Important-class kernel vulnerability.

Theoretical worst case is memory exhaustion after repeated failures. Realistic evidence supports only a small memory leak on a privileged, platform-specific error path. There is no demonstrated memory corruption primitive and no plausible LPE path from the supplied patch.

## 5. One-sentence report phrase

A privileged Qualcomm remoteproc minidump error path can leak allocated region name strings when custom coredump segment creation fails, potentially causing minor resource exhaustion only after repeated failures.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as an auto-close candidate unless the affected product exposes remoteproc crash or minidump control to untrusted users or has evidence of repeated attacker-triggerable failures.

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

Patch: remoteproc: qcom: Fix leak when custom dump_segments addition fails
Commit: 65104d6eb43f066dcf73ca9ade6478824b17d867
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=65104d6eb43f066dcf73ca9ade6478824b17d867

Commit description:

Free allocated minidump_region 'name' in qcom_add_minidump_segments()
when failing before adding the region to 'dump_segments'. Otherwise,
the 'name' is not tracked and is never freed by qcom_minidump_cleanup().

Return error when adding to 'dump_segments' fails.

Cc: stable@vger.kernel.org # v5.11
Fixes: 8ed8485 ("remoteproc: qcom: Add capability to collect minidumps")
Reviewed-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Signed-off-by: Wasim Nazir <wasim.nazir@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260318-rproc-memleak-v2-1-ade70ab858f2@oss.qualcomm.com
Signed-off-by: Bjorn Andersson <andersson@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/remoteproc/qcom_common.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=65104d6eb43f066dcf73ca9ade6478824b17d867

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

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

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:H/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.1

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: 1

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).