CVE-2024-27045: drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()'
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()'
Tell snprintf() to store at most 10 bytes in the output buffer
instead of 30.
Fixes the below:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_debugfs.c:1508 dp_dsc_clock_en_read() error: snprintf() is printing too much 30 vs 10
Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver diagnostic function could write beyond a 10-byte buffer because it allowed up to 30 bytes of output. Successful exploitation could seriously affect confidentiality, integrity, or availability, but the supplied scoring describes a local, high-complexity attack requiring low privileges.
Executive priority
Treat this as a high-priority kernel maintenance issue for affected AMD graphics systems, especially shared endpoints or workstations with untrusted local users. It does not warrant an internet-wide emergency response based on current evidence, because attack access is local, complexity is high, and active exploitation is not established.
Technical view
The flaw is in dp_dsc_clock_en_read() within amdgpu_dm_debugfs.c. An snprintf() size argument permitted 30 bytes for a 10-byte destination. Linux stable fixes constrain output to 10 bytes. CVSS 3.1 is 7.0: local access, high complexity, low privileges, no user interaction, and high potential impact.
Likely exposure
Exposure is most plausible on affected Linux kernels using the AMDGPU display component. The bundle identifies versions beginning with 5.9 and several affected or boundary releases, but does not provide a complete distribution-specific version matrix. Confirm status using vendor kernel advisories and backport records.
Exploitation context
The supplied CVSS vector indicates exploitation requires local access, low privileges, and high complexity. No user interaction is required. The bundle says this CVE is not in KEV and provides no evidence of active exploitation, public proof-of-concept availability, or demonstrated real-world impact.
Researcher notes
The root cause is a size mismatch passed to snprintf(), corrected from 30 to 10 bytes. The bundle supplies no CWE, exploit demonstration, reachable-input analysis, or proof that every listed release is practically exploitable. Researchers should distinguish source-level presence from reachable exposure and consult distribution backport data.
Mitigation direction
Install a vendor-supported kernel containing the applicable Linux stable fix or confirmed backport.
Prioritize multi-user systems where untrusted local users can access the affected AMD display diagnostic interface.
If immediate updating is impossible, review vendor guidance for supported temporary exposure-reduction measures.
Reboot into the corrected kernel after installation and retain rollback procedures.
Validation and detection
Record the running kernel version and distribution package release on systems using AMD graphics.
Check vendor advisories and package changelogs for an explicit CVE-2024-27045 fix or backport.
Verify source or build provenance includes the applicable referenced Linux stable commit.
After reboot, confirm the corrected kernel is running and normal AMD display functionality remains stable.
Review kernel logs for AMDGPU faults, memory errors, or unexplained crashes.
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.
cve · low confidence lookup
CVE-2024-27045 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.