From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72387: drm/panthor: Fix potential invalid pointer deref in group_process_tiler_oom()
Date: Sat, 15 Aug 2026 15:07:46 +0900 [thread overview]
Message-ID: <2026081519-CVE-2026-72387-5e11@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/panthor: Fix potential invalid pointer deref in group_process_tiler_oom()
If heaps is an ERR_PTR(), panthor_heap_pool_put() will deref an invalid
pointer. Make sure we set it to NULL in that case.
The Linux kernel CVE team has assigned CVE-2026-72387 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit de85488138247d034eb3241840424a54d660926b and fixed in 6.12.97 with commit bfc5b91ab3ddddf636d8c1c050455bf4e14c912b
Issue introduced in 6.10 with commit de85488138247d034eb3241840424a54d660926b and fixed in 6.18.40 with commit dd0b2976b7c0f4ea806855ed19ffad967d36610e
Issue introduced in 6.10 with commit de85488138247d034eb3241840424a54d660926b and fixed in 7.1.5 with commit 053522ba615888e874adc04e675d9ed2e13f35af
Issue introduced in 6.10 with commit de85488138247d034eb3241840424a54d660926b and fixed in 7.2-rc2 with commit b39436d0ba1571dbcda69d20ec567344b3eecfc7
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-72387
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/gpu/drm/panthor/panthor_sched.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/bfc5b91ab3ddddf636d8c1c050455bf4e14c912b
https://git.kernel.org/stable/c/dd0b2976b7c0f4ea806855ed19ffad967d36610e
https://git.kernel.org/stable/c/053522ba615888e874adc04e675d9ed2e13f35af
https://git.kernel.org/stable/c/b39436d0ba1571dbcda69d20ec567344b3eecfc7
reply other threads:[~2026-08-15 6:25 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=2026081519-CVE-2026-72387-5e11@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.