CVE-2024-49894: drm/amd/display: Fix index out of bounds in degamma hardware format translation
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix index out of bounds in degamma hardware format translation
Fixes index out of bounds issue in
`cm_helper_translate_curve_to_degamma_hw_format` function. The issue
could occur when the index 'i' exceeds the number of transfer function
points (TRANSFER_FUNC_POINTS).
The fix adds a check to ensure 'i' is within bounds before accessing the
transfer function points. If 'i' is out of bounds the function returns
false to indicate an error.
Reported by smatch:
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max
Security readout for executives and security teams
Plain-English summary
A bounds-checking flaw in the Linux AMD display driver can access transfer-function data outside its valid range. A low-privileged local user may be able to cause serious information disclosure or system disruption. It is not remotely exploitable according to the supplied CVSS vector.
Executive priority
Treat this as a high-priority endpoint and multi-user Linux remediation, especially where AMD graphics and untrusted local accounts coexist. It is less urgent than an internet-exploitable flaw, but the stated confidentiality and availability impacts justify prompt patching through normal kernel-maintenance procedures.
Technical view
The flaw is in cm_helper_translate_curve_to_degamma_hw_format within the AMD DRM display code. The index i can exceed TRANSFER_FUNC_POINTS before accessing red, green, and blue transfer-function arrays. Stable-kernel fixes reject the operation by returning false when the index is out of bounds.
Likely exposure
Exposure is limited to Linux systems using the affected AMD GPU display-driver path. Multi-user workstations and systems granting untrusted users local access deserve greater attention. The supplied affected-version data is irregular, so kernel version alone may not reliably determine exposure where distributions backport fixes.
Exploitation context
The supplied CVSS 3.1 vector scores 7.1 and requires local access with low privileges, without user interaction. It indicates potential high confidentiality and availability impact but no integrity impact. The record is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
Smatch identified possible out-of-bounds accesses involving 1,025 transfer-function entries. The patch adds an explicit bounds check before array access. The bundle lists multiple stable commits, consistent with backports across kernel branches. Exact affected and fixed ranges are not cleanly expressed, so confirm status against the relevant distribution or product advisory.
Mitigation direction
Install a vendor-supported kernel update containing the applicable stable-kernel fix.
Reboot into the updated kernel so the corrected AMD display module is active.
Consult distribution or appliance-vendor guidance when package backports make upstream version comparisons inconclusive.
Limit untrusted local access until affected systems can be updated.
Validation and detection
Inventory Linux systems with AMD graphics and record their running kernel packages.
Check vendor advisories and package changelogs for CVE-2024-49894 or the referenced stable fixes.
Confirm systems booted into the corrected kernel after updating.
Verify vulnerability scanners recognize distribution backports rather than relying solely on upstream version numbers.
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-49894 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.