CVE-2024-46812: drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Skip inactive planes within ModeSupportAndSystemConfiguration
[Why]
Coverity reports Memory - illegal accesses.
[How]
Skip inactive planes.
Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver flaw can make the kernel access memory illegally while evaluating display configurations containing inactive planes. On affected systems, a local low-privileged user could potentially compromise confidentiality, integrity, or availability. Exposure is primarily relevant to Linux machines using the affected AMD display path.
Executive priority
Treat as a high-priority endpoint patching issue where affected AMD graphics and local untrusted access coexist. It is less urgent for systems that cannot reach the AMD display path. Require evidence of the corrected running kernel, not merely an installed package.
Technical view
The flaw is in drm/amd/display within ModeSupportAndSystemConfiguration. The correction skips inactive planes before processing them. CVSS 3.1 scores it 7.8 with local access, low complexity, low privileges, no user interaction, unchanged scope, and high potential confidentiality, integrity, and availability impact.
Likely exposure
Prioritize Linux workstations, shared desktops, and other systems using AMD graphics with an affected kernel. Systems without the AMD display driver or relevant hardware are less likely to expose this path. The supplied version data is ambiguous, so confirm applicability through distribution advisories and backport records.
Exploitation context
The CVSS vector describes local, low-privileged exploitation without user interaction; this is not a remote-entry vulnerability. The source bundle reports no KEV listing and provides no evidence of active exploitation, public proof-of-concept code, or a demonstrated attack chain.
Researcher notes
Coverity identified an illegal memory access, and the upstream fix skips inactive planes. No CWE, root-cause depth, crash trace, exploit demonstration, or precise affected-version ranges are supplied. The repeated commit hash and mixed version list reduce confidence in exact exposure mapping; assess fixes through commit or vendor-backport provenance.
Mitigation direction
Install a distribution kernel containing the applicable upstream stable correction.
Prioritize shared or untrusted-user systems operating with affected AMD graphics.
If immediate updating is unavailable, consult the distribution vendor for supported mitigations.
Reboot into the corrected kernel after installation.
Validation and detection
Record the running kernel version and identify whether the AMD display driver is active.
Check distribution advisories and package changelogs for a backport of the listed correction.
Confirm the system booted into the updated kernel after remediation.
Review kernel logs for AMD display faults or memory-access-related 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-46812 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.