CVE-2026-64049: drm/msm/adreno: fix userspace-triggered crash on a2xx-a4xx

CVE-2026-64049: drm/msm/adreno: fix userspace-triggered crash on a2xx-a4xx

[Greg Kroah-Hartman]

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

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

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

drm/msm/adreno: fix userspace-triggered crash on a2xx-a4xx

Before a5xx Adreno driver will not try fetching UBWC params (because
those generations didn't support UBWC anyway), however it's still
possible to query UBWC-related params from the userspace, triggering
possible NULL pointer dereference. Check for UBWC config in
adreno_get_param() and return sane defaults if there is none.

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

The Linux kernel CVE team has assigned CVE-2026-64049 to this issue.


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

	Issue introduced in 6.17 with commit a452510aad53f665eb422784ff525c4889aa246f and fixed in 6.18.34 with commit eea43d5ed45089705bc5d70971c39076962d5951
	Issue introduced in 6.17 with commit a452510aad53f665eb422784ff525c4889aa246f and fixed in 7.0.11 with commit 22fc33d9b67694b24e0deb3f08c622464338cecb
	Issue introduced in 6.17 with commit a452510aad53f665eb422784ff525c4889aa246f and fixed in 7.1 with commit 2b4abf879360ea00a9e2b46d2d15dcdbc0687eed

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-64049
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/adreno_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/eea43d5ed45089705bc5d70971c39076962d5951
	https://git.kernel.org/stable/c/22fc33d9b67694b24e0deb3f08c622464338cecb
	https://git.kernel.org/stable/c/2b4abf879360ea00a9e2b46d2d15dcdbc0687eed