In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix out-of-bound accesses
[WHAT & HOW]
hpo_stream_to_link_encoder_mapping has size MAX_HPO_DP2_ENCODERS(=4),
but location can have size up to 6. As a result, it is necessary to
check location against MAX_HPO_DP2_ENCODERS.
Similiarly, disp_cfg_stream_location can be used as an array index which
should be 0..5, so the ASSERT's conditions should be less without equal.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s AMD display driver can read or write beyond intended array boundaries. Exploitation requires local, low-privileged access according to the supplied CVSS vector. Successful exploitation could seriously affect confidentiality, integrity, and availability, but the sources do not describe a demonstrated exploit or specific real-world outcome.
Executive priority
Treat this as a high-priority patching issue for affected Linux systems using AMD display functionality, particularly where untrusted users receive local accounts. It is not described as remotely exploitable, actively exploited, or KEV-listed in the supplied evidence, so prioritization should consider local-access exposure and asset importance.
Technical view
The AMD display code can index the four-entry hpo_stream_to_link_encoder_mapping array using larger location values. A related assertion can permit an invalid boundary value for disp_cfg_stream_location, whose valid indices are 0 through 5. The supplied CVSS score is 7.8 with local access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is limited to Linux systems containing the affected AMD display code and relevant runtime configuration. The bundle identifies affected kernel version data, including 6.12.20, 6.13.8, and 6.14, but does not clearly define complete version ranges or distribution-specific package status. Confirm exact builds with kernel or distribution guidance.
Exploitation context
The supplied vector indicates local exploitation requiring low privileges; it does not indicate a network attack. The bundle marks KEV false and provides no cited evidence of active exploitation or public weaponization. This does not establish that exploitation is impossible or absent.
Researcher notes
The core defect involves unchecked or incorrectly bounded array indices in drm/amd/display. The mapping has four entries, while location may exceed that boundary; a second index must remain within 0 through 5. The sources do not identify a CWE, reliable trigger, demonstrated impact, exploit chain, or complete commit-to-version mapping.
Mitigation direction
Install a vendor kernel update that incorporates the applicable upstream stable fix.
Confirm distribution-specific remediation guidance because the supplied version boundaries are incomplete.
Reboot affected systems into the updated kernel after installation.
Limit untrusted local access until patched; this reduces exposure but does not remove the vulnerable code.
Validation and detection
Inventory Linux kernel builds on systems using AMD display functionality.
Compare exact kernel packages against distribution advisories and the referenced stable fixes.
Verify the running kernel after reboot, not only the installed package version.
Confirm applicable fix commits are present when maintaining custom kernels.
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-2025-21985 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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
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.