# CVE-2026-72216: remoteproc: qcom: Fix leak when custom dump_segments addition fails

> A memory leak in the Linux kernel's Qualcomm remoteproc driver allows attackers to cause denial of service by triggering a failure in minidump segment addition.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72216, DEBIAN-CVE-2026-72216, GHSA-hpxv-9w4f-7523, UBUNTU-CVE-2026-72216

## What is CVE-2026-72216?

CVE-2026-72216 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

remoteproc: qcom: Fix leak when custom dump_segments addition fails

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.

## Which versions are affected by CVE-2026-72216?


## How do I fix CVE-2026-72216?

Apply the vendor's patch.

## Is CVE-2026-72216 being exploited?

There is no known exploitation of CVE-2026-72216 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72216 and fix it if it is affected.

What it is: CVE-2026-72216 is a memory corruption vulnerability in Linux, published on 15 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-72216 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72216/ (Markdown: https://insights.sbomify.com/CVE-2026-72216/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72216
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72216
- OSV: https://osv.dev/vulnerability/CVE-2026-72216

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72216/
Summaries are generated and may contain mistakes; the official description above is the record.