linux-cve-announce - CVE-2024-58052: drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2025030605-CVE-2024-58052-c947@gregkh>
Date: Thu,  6 Mar 2025 16:54:05 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-58052: drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table

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

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

drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table

The function atomctrl_get_smc_sclk_range_table() does not check the return
value of smu_atom_get_data_table(). If smu_atom_get_data_table() fails to
retrieve SMU_Info table, it returns NULL which is later dereferenced.

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

In practice this should never happen as this code only gets called
on polaris chips and the vbios data table will always be present on
those chips.

The Linux kernel CVE team has assigned CVE-2024-58052 to this issue.


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

	Issue introduced in 4.7 with commit a23eefa2f4615af91ea496ca5b55c9e7c6fa934c and fixed in 6.1.129 with commit ae522ad211ec4b72eaf742b25f24b0a406afcba1
	Issue introduced in 4.7 with commit a23eefa2f4615af91ea496ca5b55c9e7c6fa934c and fixed in 6.6.76 with commit 6a30634a2e0f1dd3c6b39fd0f114c32893a9907a
	Issue introduced in 4.7 with commit a23eefa2f4615af91ea496ca5b55c9e7c6fa934c and fixed in 6.12.13 with commit 0b97cd8a61b2b40fd73cf92a4bb2256462d22adb
	Issue introduced in 4.7 with commit a23eefa2f4615af91ea496ca5b55c9e7c6fa934c and fixed in 6.13.2 with commit 396350adf0e5ad4bf05f01e4d79bfb82f0f6c41a
	Issue introduced in 4.7 with commit a23eefa2f4615af91ea496ca5b55c9e7c6fa934c and fixed in 6.14-rc1 with commit 357445e28ff004d7f10967aa93ddb4bffa5c3688

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-2024-58052
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/amd/pm/powerplay/hwmgr/ppatomctrl.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/ae522ad211ec4b72eaf742b25f24b0a406afcba1
	https://git.kernel.org/stable/c/6a30634a2e0f1dd3c6b39fd0f114c32893a9907a
	https://git.kernel.org/stable/c/0b97cd8a61b2b40fd73cf92a4bb2256462d22adb
	https://git.kernel.org/stable/c/396350adf0e5ad4bf05f01e4d79bfb82f0f6c41a
	https://git.kernel.org/stable/c/357445e28ff004d7f10967aa93ddb4bffa5c3688