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.
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 6.8.0-64.67 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 6.8.0-1032.34 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1084.91~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1146.156~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-6.8 | — | 6.8.0-1032.34~22.04.1 |
| linux-aws-fips | — | 5.15.0-1084.91+fips1 |
| linux-aws-hwe | — | — |
| linux-azure | — | 6.8.0-1034.39 |
| linux-azure-4.15 | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1089.98~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1151.158~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.11 | — | 6.11.0-1015.15~24.04.1 |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-6.8 | — | 6.8.0-1034.39~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | 5.15.0-1089.98+fips1 |
| linux-azure-nvidia | — | 6.8.0-1022.23 |
| linux-bluefield | — | — |
| linux-fips | — | 6.8.0-78.78+fips1 |
| linux-gcp | — | 6.8.0-1033.35 |
| linux-gcp-4.15 | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1083.92~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1149.158~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.11 | — | 6.11.0-1015.15~24.04.1 |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-6.8 | — | 6.8.0-1033.35~22.04.1 |
| linux-gcp-fips | — | 5.15.0-1083.92+fips1 |
| linux-gke | — | 6.8.0-1028.32 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 6.8.0-1015.17 |
| linux-gkeop-5.15 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-142.152~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-216.236~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.11 | — | 6.11.0-26.26~24.04.1 |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-6.8 | — | 6.8.0-64.67~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 6.8.0-1029.29 |
| linux-ibm-5.15 | — | 5.15.0-1076.79~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1092.97~18.04.1 |
| linux-ibm-6.8 | — | 6.8.0-1029.29~22.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1077.79 |
| linux-intel-iotg | — | 5.15.0-1079.85 |
| linux-intel-iotg-5.15 | — | 5.15.0-1079.85~20.04.1 |
| linux-iot | — | 5.4.0-1051.54 |
| linux-kvm | — | 5.15.0-1080.85 |
| linux-lowlatency | — | 6.8.0-64.67.1 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-140.150~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.11 | — | 6.11.0-1014.15~24.04.1 |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-lowlatency-hwe-6.8 | — | 6.8.0-64.67.1~22.04.1 |
| linux-nvidia | — | 6.8.0-1031.34 |
| linux-nvidia-6.11 | — | 6.11.0-1010.10 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-6.8 | — | 6.8.0-1031.34~22.04.1 |
| linux-nvidia-lowlatency | — | 6.8.0-1031.34.1 |
| linux-nvidia-tegra | — | 6.8.0-1008.8 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1039.39~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1026.26 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | 6.11.0-1022.22 |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | 6.8.0-1031.31 |
| linux-oracle | — | 6.8.0-1029.30 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1081.87~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1144.154~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-oracle-6.8 | — | 6.8.0-1029.30~22.04.1 |
| linux-raspi | — | 6.8.0-1031.35 |
| linux-raspi-5.4 | — | 5.4.0-1129.142~18.04.1 |
| linux-raspi-realtime | — | 6.8.0-2026.27 |
| linux-raspi2 | — | — |
| linux-realtime | — | 6.8.1-1025.26 |
| linux-realtime-6.8 | — | 6.8.1-1025.26~22.04.1 |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1079.83~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-riscv-6.8 | — | 6.8.0-64.67~22.04.1 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx | — | 6.8.0-1017.18 |
| linux-xilinx-zynqmp | — | 5.15.0-1050.54 |
References
Similar Threats
- Unknown CGA-23jx-hhcx-m389
- Unknown CGA-2qp7-6757-fmgc
- Unknown CGA-2rj5-jc55-r267
- Unknown CGA-3m96-cwq8-6xmx
- Unknown CGA-3qj9-973w-fh9g
Free Vulnerability Check
Is your WordPress site affected?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
