CVE-2024-42064: drm/amd/display: Skip pipe if the pipe idx not set properly
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Skip pipe if the pipe idx not set properly
[why]
Driver crashes when pipe idx not set properly
[how]
Add code to skip the pipe that idx not set properly
Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver flaw can crash the system when a display pipeline has an improperly set index. The supplied CVSS assessment also indicates possible confidentiality and integrity impact, although the source description documents only a driver crash. Exploitation requires local, low-privileged access and no user interaction.
Executive priority
Treat as a high-priority endpoint stability issue where affected AMD graphics and untrusted local access coincide. Patch through normal expedited kernel maintenance after vendor confirmation. It is less urgent for systems without the applicable driver, and the supplied evidence does not support emergency action for active exploitation.
Technical view
CVE-2024-42064 affects Linux kernel drm/amd/display handling. An improperly initialized pipe index can reach driver processing and cause a crash. The upstream correction skips pipes whose index is not properly set. The supplied record lists affected Linux versions including 6.7, 6.9.8, and 6.10, but its version-boundary data is ambiguous.
Likely exposure
Exposure is most plausible on systems running an affected Linux kernel with the AMD display driver active. Desktops, workstations, and shared systems permitting untrusted local access deserve attention. Systems without applicable AMD display hardware or driver use are less likely exposed, but distribution backports must be checked.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges, with no user interaction. The supplied bundle says this CVE is not in KEV and provides no evidence of active exploitation or a public exploit. The documented outcome is a driver crash; broader impacts come from the CVSS assessment.
Researcher notes
The source identifies invalid pipe-index handling and a defensive skip as the correction. No CWE is assigned. The CVSS claims high confidentiality, integrity, and availability impact, but the terse technical description substantiates only a crash. Exact vulnerable boundaries and downstream backports require distribution-specific confirmation.
Mitigation direction
Install a vendor-supported kernel containing the applicable cited stable fix or documented backport.
Prioritize shared systems and AMD-equipped endpoints where untrusted users can obtain local access.
Consult the Linux distribution's advisory for exact fixed package versions and reboot requirements.
Restrict unnecessary local accounts until affected systems are updated.
Validation and detection
Record the running kernel version and compare it with the distribution's CVE advisory.
Confirm whether applicable AMD graphics hardware and the AMD display driver are present and active.
Verify the installed kernel contains either cited fix or an equivalent vendor backport.
Review kernel logs for AMD display-driver crashes; absence of crashes does not prove safety.
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-42064 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.