Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-36969drm/amd/display: Fix division by zero in setup_dsc_config

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-36969, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < a32c8f951c8a456c1c251e1dcdf21787f8066445
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 91402e0e5de9124a3108db7a14163fcf9a6d322f
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 7e4f50dfc98c49b3dc6875a35c3112522fb25639
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < f187fcbbb8f8bf10c6687f0beae22509369f7563
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 308de6be0c9c7ba36915c0d398e771725c0ea911
    • affected 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c – < 130afc8a886183a94cf6eab7d24f300014ff87ba
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.15.160 – ≤ 5.15.*
    • unaffected 6.1.92 – ≤ 6.1.*
    • unaffected 6.6.32 – ≤ 6.6.*
    • unaffected 6.8.11 – ≤ 6.8.*
    • unaffected 6.9.2 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-36969 badge
[![CVE-2024-36969](https://cveledger.app/badge/CVE-2024-36969.svg)](https://cveledger.app/cve/CVE-2024-36969)

Record last updated .