Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 130afc8a886183a94cf6eab7d24f300014ff87ba, 308de6be0c9c7ba36915c0d398e771725c0ea911, 7e4f50dfc98c49b3dc6875a35c3112522fb25639.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 130afc8a886183a94cf6eab7d24f300014ff87ba, 308de6be0c9c7ba36915c0d398e771725c0ea911, 7e4f50dfc98c49b3dc6875a35c3112522fb25639 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jun 8, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-36969

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 5.15.160
  • linux linux kernel5.16 and later · before 6.1.92
  • linux linux kernel6.2 and later · before 6.6.32
  • linux linux kernel6.7 and later · before 6.8.11
  • linux linux kernel6.9 and later · before 6.9.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.15affected
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before a32c8f951c8a456c1c251e1dcdf21787f8066445affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 91402e0e5de9124a3108db7a14163fcf9a6d322faffected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 7e4f50dfc98c49b3dc6875a35c3112522fb25639affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before f187fcbbb8f8bf10c6687f0beae22509369f7563affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 308de6be0c9c7ba36915c0d398e771725c0ea911affected · git
    • 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c and later · before 130afc8a886183a94cf6eab7d24f300014ff87baaffected · git
    • before 4.15not affected · semver
    • 5.15.160 and later · up to and including 5.15.*not affected · semver
    • 6.1.92 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.8.11-16.8.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-36966Jun 8, 2024 · erofs: reliably distinguish block based and fscache mode
    22Monitor
  • ← EarlierCVE-2024-36967Jun 8, 2024 · KEYS: trusted: Fix memory leak in tpm2_key_encode()
    22Monitor
  • Later →CVE-2024-36970Jun 8, 2024 · wifi: iwlwifi: Use request_module_nowait
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux130afc8a886183a94cf6eab7d24f300014ff87baVendor (CNA)
Linux Linux308de6be0c9c7ba36915c0d398e771725c0ea911Vendor (CNA)
Linux Linux7e4f50dfc98c49b3dc6875a35c3112522fb25639Vendor (CNA)
Linux Linux91402e0e5de9124a3108db7a14163fcf9a6d322fVendor (CNA)
Linux Linuxa32c8f951c8a456c1c251e1dcdf21787f8066445Vendor (CNA)
Linux Linuxf187fcbbb8f8bf10c6687f0beae22509369f7563Vendor (CNA)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-2694538 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case
    33Monitor
  • CVE-2024-369059 days aparttcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets
    22Monitor
  • CVE-2021-4758411 days apartiocost: Fix divide-by-zero on donation from low hweight cgroup
    22Monitor
  • CVE-2021-4760611 days apartnet: netlink: af_netlink: Prevent empty skb by adding a check on len.
    22Monitor
  • CVE-2021-4749517 days apartusbnet: sanity check for maxpacket
    22Monitor
  • CVE-2021-4736318 days apartnexthop: Fix division by zero while replacing a resilient group
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-369 · Divide By Zero

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records