CVE-2024-57950: drm/amd/display: Initialize denominator defaults to 1
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Initialize denominator defaults to 1
[WHAT & HOW]
Variables, used as denominators and maybe not assigned to other values,
should be initialized to non-zero to avoid DIVIDE_BY_ZERO, as reported
by Coverity.
(cherry picked from commit e2c4c6c10542ccfe4a0830bb6c9fd5b177b7bbb7)
Security readout for executives and security teams
Plain-English summary
CVE-2024-57950 is a Linux kernel AMD display driver issue where an uninitialized denominator could cause divide-by-zero behavior. The reported impact is availability only: a local low-privileged user could potentially trigger a crash or denial of service. The provided sources do not show active exploitation.
Executive priority
Treat this as a routine but real availability fix. Prioritize patching AMD GPU Linux endpoints and any shared workstations, but it does not warrant emergency response without evidence of exploitation or critical business dependency.
Technical view
The flaw is CWE-369 in drm/amd/display. The kernel fix initializes denominator defaults to 1 so later calculations cannot divide by zero when variables were not assigned other values. CVSS 3.1 is 5.5, local attack vector, low complexity, low privileges, no user interaction, availability high.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with AMD display driver code paths. The source bundle lists Linux 6.11, 6.12.12, and 6.13 as affected, but distro backports may change practical exposure.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not cite active exploitation. The vulnerability is local and privilege-required, so business risk is primarily service disruption on affected endpoints or workstations, not remote compromise.
Researcher notes
Evidence points to a defensive initialization fix discovered by Coverity, not a detailed public exploit. Validate exposure through kernel version, vendor backport status, and AMD display driver presence. Do not assume every listed upstream version maps directly to distro package vulnerability.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution advisories for backported fixes in maintained kernels.
Prioritize systems with AMD GPUs or AMD display driver usage.
Avoid unsupported kernels where vendor fix status is unclear.
Validation and detection
Inventory Linux hosts running affected kernel versions.
Confirm whether AMD display driver code is present or in use.
Verify the kernel package includes the referenced stable commits.
Review crash logs for divide-by-zero events in AMD display paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-369: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-369 · source CWE mapping
Divide By Zero
Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.