linux-cve-announce - CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025070413-CVE-2025-38188-e0a5@gregkh>
Date: Fri,  4 Jul 2025 15:37:17 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38188: drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

drm/msm/a7xx: Call CP_RESET_CONTEXT_STATE

Calling this packet is necessary when we switch contexts because there
are various pieces of state used by userspace to synchronize between BR
and BV that are persistent across submits and we need to make sure that
they are in a "safe" state when switching contexts. Otherwise a
userspace submission in one context could cause another context to
function incorrectly and hang, effectively a denial of service (although
without leaking data). This was missed during initial a7xx bringup.

Patchwork: https://patchwork.freedesktop.org/patch/654924/

The Linux kernel CVE team has assigned CVE-2025-38188 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.7 with commit af66706accdf5afef45204afc87037f876e0665c and fixed in 6.12.35 with commit 8a1f52651dd8203695d293c6824d8f6c067877d1
	Issue introduced in 6.7 with commit af66706accdf5afef45204afc87037f876e0665c and fixed in 6.15.4 with commit 35fe72f3c425bbf1d580bd9066e2456b1dbae4a8
	Issue introduced in 6.7 with commit af66706accdf5afef45204afc87037f876e0665c and fixed in 6.16-rc3 with commit 2b520c6104f34e3a548525173c38ebca4402cac3

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-2025-38188
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/msm/adreno/a6xx_gpu.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/8a1f52651dd8203695d293c6824d8f6c067877d1
	https://git.kernel.org/stable/c/35fe72f3c425bbf1d580bd9066e2456b1dbae4a8
	https://git.kernel.org/stable/c/2b520c6104f34e3a548525173c38ebca4402cac3