drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a23eefa2f4615af91ea496ca5b55c9e7c6fa934c · < 0b97cd8a61b2b40fd73cf92a4bb2256462d22adb| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s amdgpu driver can dereference a NULL pointer if it fails to retrieve the SMU_Info table. This could cause a crash, but the affected code runs only on Polaris chips, where the table is expected to be present. The input does not identify an attacker path or authentication or user-interaction requirements.
Engineers running Linux kernels with the amdgpu driver on Polaris chips should check their kernel version; affected versions are not specified.