linux-cve-announce - CVE-2025-21996: drm/radeon: fix uninitialized size issue in radeon_vce_cs

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: <2025040348-CVE-2025-21996-8e4a@gregkh>
Date: Thu,  3 Apr 2025 08:17:48 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21996: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()

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

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

drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse()

On the off chance that command stream passed from userspace via
ioctl() call to radeon_vce_cs_parse() is weirdly crafted and
first command to execute is to encode (case 0x03000001), the function
in question will attempt to call radeon_vce_cs_reloc() with size
argument that has not been properly initialized. Specifically, 'size'
will point to 'tmp' variable before the latter had a chance to be
assigned any value.

Play it safe and init 'tmp' with 0, thus ensuring that
radeon_vce_cs_reloc() will catch an early error in cases like these.

Found by Linux Verification Center (linuxtesting.org) with static
analysis tool SVACE.

(cherry picked from commit 2d52de55f9ee7aaee0e09ac443f77855989c6b68)

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


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

	Issue introduced in 3.15 with commit 2fc5703abda201f138faf63bdca743d04dbf4b1a and fixed in 6.1.132 with commit 78b07dada3f02f77762d0755a96d35f53b02be69
	Issue introduced in 3.15 with commit 2fc5703abda201f138faf63bdca743d04dbf4b1a and fixed in 6.6.85 with commit 3ce08215cad55c10a6eeeb33d3583b6cfffe3ab8
	Issue introduced in 3.15 with commit 2fc5703abda201f138faf63bdca743d04dbf4b1a and fixed in 6.12.21 with commit dd1801aa01bba1760357f2a641346ae149686713
	Issue introduced in 3.15 with commit 2fc5703abda201f138faf63bdca743d04dbf4b1a and fixed in 6.13.9 with commit f5e049028124f755283f2c07e7a3708361ed1dc8
	Issue introduced in 3.15 with commit 2fc5703abda201f138faf63bdca743d04dbf4b1a and fixed in 6.14 with commit dd8689b52a24807c2d5ce0a17cb26dc87f75235c

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-21996
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/radeon/radeon_vce.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/78b07dada3f02f77762d0755a96d35f53b02be69
	https://git.kernel.org/stable/c/3ce08215cad55c10a6eeeb33d3583b6cfffe3ab8
	https://git.kernel.org/stable/c/dd1801aa01bba1760357f2a641346ae149686713
	https://git.kernel.org/stable/c/f5e049028124f755283f2c07e7a3708361ed1dc8
	https://git.kernel.org/stable/c/dd8689b52a24807c2d5ce0a17cb26dc87f75235c