From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72216: remoteproc: qcom: Fix leak when custom dump_segments addition fails
Date: Sat, 15 Aug 2026 15:04:55 +0900 [thread overview]
Message-ID: <2026081546-CVE-2026-72216-9784@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-72216 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.11 with commit 8ed8485c4f056d488d17a2b56581c86aeb42955d and fixed in 6.6.145 with commit 65104d6eb43f066dcf73ca9ade6478824b17d867
Issue introduced in 5.11 with commit 8ed8485c4f056d488d17a2b56581c86aeb42955d and fixed in 6.12.97 with commit 381c8a7a59da06293951c343857f4a2465b2c655
Issue introduced in 5.11 with commit 8ed8485c4f056d488d17a2b56581c86aeb42955d and fixed in 6.18.40 with commit 51aad3d89a2dd2bd34713785b0f2fd5177eb33b6
Issue introduced in 5.11 with commit 8ed8485c4f056d488d17a2b56581c86aeb42955d and fixed in 7.1.5 with commit e5b1aaa74118e91f0c0f18b22b6f853199873db4
Issue introduced in 5.11 with commit 8ed8485c4f056d488d17a2b56581c86aeb42955d and fixed in 7.2-rc1 with commit ecf9fc18e62c58eae1ceb65dab2bccb8a724de2d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-72216
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/remoteproc/qcom_common.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/65104d6eb43f066dcf73ca9ade6478824b17d867
https://git.kernel.org/stable/c/381c8a7a59da06293951c343857f4a2465b2c655
https://git.kernel.org/stable/c/51aad3d89a2dd2bd34713785b0f2fd5177eb33b6
https://git.kernel.org/stable/c/e5b1aaa74118e91f0c0f18b22b6f853199873db4
https://git.kernel.org/stable/c/ecf9fc18e62c58eae1ceb65dab2bccb8a724de2d
reply other threads:[~2026-08-15 6:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081546-CVE-2026-72216-9784@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.