Vulnerability · Published Jun 8, 2024 · Assigned by Linux
CVE-2024-36969drm/amd/display: Fix division by zero in setup_dsc_config
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 12% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix division by zero in setup_dsc_config When slice_height is 0, the division by slice_height in the calculation of the number of slices will cause a division by zero driver crash. This leaves the kernel in a state that requires a reboot. This patch adds a check to avoid the division by zero. The stack trace below is for the 6.8.4 Kernel. I reproduced the issue on a Z16 Gen 2 Lenovo Thinkpad with a Apple Studio Display monitor connected via Thunderbolt. The amdgpu driver crashed with this exception when I rebooted the system with the monitor connected. kernel: ? die (arch/x86/kernel/dumpstack.c:421 arch/x86/kernel/dumpstack.c:434 arch/x86/kernel/dumpstack.c:447) kernel: ? do_trap (arch/x86/kernel/traps.c:113 arch/x86/kernel/traps.c:154) kernel: ? setup_dsc_config (drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/dc_dsc.c:1053) amdgpu kernel: ? do_error_trap (./arch/x86/include/asm/traps.h:58 arch/x86/kernel/traps.c:175) kernel: ? setup_dsc_config (drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/dc_dsc.c:1053) amdgpu kernel: ? exc_divide_error (arch/x86/kernel/traps.c:194 (discriminator 2)) kernel: ? setup_dsc_config (drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/dc_dsc.c:1053) amdgpu kernel: ? asm_exc_divide_error (./arch/x86/include/asm/idtentry.h:548) kernel: ? setup_dsc_config (drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/dc_dsc.c:1053) amdgpu kernel: dc_dsc_compute_config (drivers/gpu/drm/amd/amdgpu/../display/dc/dsc/dc_dsc.c:1109) amdgpu After applying this patch, the driver no longer crashes when the monitor is connected and the system is rebooted. I believe this is the same issue reported for 3113.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.94-1 | DEBIAN-CVE-2024-36969 |
| Debian:13 | linux | 6.8.11-1 | DEBIAN-CVE-2024-36969 |
| Debian:14 | linux | 6.8.11-1 | DEBIAN-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux | 5.15.0-118.128 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux | 5.15.0-118.128 | USN-6950-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-40.40 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1067.73 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1067.73 | USN-6950-1 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1013.14 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1013.14~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1070.79 | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1012.14 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1012.14~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1070.79.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1066.74 | USN-6950-1 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1066.74 | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1012.13 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1012.13~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1064.70 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1064.70 | USN-6950-1 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1008.11 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1050.57 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1050.57 | USN-6950-1 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-40.40~22.04.3 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1060.63 | USN-6950-2 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1060.63 | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1010.10 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1010.10~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1062.68 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1062.68 | USN-6950-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1064.69 | USN-6950-1 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1064.69 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-118.128 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-118.128 | USN-6950-1 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-40.40.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-40.40.1~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1062.63 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1062.63 | USN-6950-1 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1011.11 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1011.11~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1011.11.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1027.27 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1015.15 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | 6.8.0-1010.10 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1065.71 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1065.71 | USN-6950-3 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1010.10 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1010.10~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1060.63 | USN-6950-2 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1060.63 | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1009.10 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:24.04:LTS | linux-riscv | 6.8.0-40.40.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-40.40.1~22.04.1 | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2024-36969 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1035.39 | UBUNTU-CVE-2024-36969 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before a32c8f951c8a456c1c251e1dcdf21787f80664454562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before 91402e0e5de9124a3108db7a14163fcf9a6d322f4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before 7e4f50dfc98c49b3dc6875a35c3112522fb256394562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before f187fcbbb8f8bf10c6687f0beae22509369f75634562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before 308de6be0c9c7ba36915c0d398e771725c0ea9114562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – before 130afc8a886183a94cf6eab7d24f300014ff87ba |
| Linux | Linux | 4.15 |
References
- https://git.kernel.org/stable/c/a32c8f951c8a456c1c251e1dcdf21787f8066445
- https://git.kernel.org/stable/c/91402e0e5de9124a3108db7a14163fcf9a6d322f
- https://git.kernel.org/stable/c/7e4f50dfc98c49b3dc6875a35c3112522fb25639
- https://git.kernel.org/stable/c/f187fcbbb8f8bf10c6687f0beae22509369f7563
- https://git.kernel.org/stable/c/308de6be0c9c7ba36915c0d398e771725c0ea911
- https://git.kernel.org/stable/c/130afc8a886183a94cf6eab7d24f300014ff87ba