CVE-2026-46263
Bounds Check Bypass in AMD Display Core Driver
Publication date: 2026-06-03
Last updated on: 2026-06-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| amd | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not include any details about the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's AMD display driver code, specifically in the drm/amd/display component. The issue arises because the variable eng_id, which can be negative or equal to 5, is used directly as an index into the stream_enc_regs[] array that only has 5 elements (indexed 0 to 4). When eng_id is 5 or negative, it causes an out-of-bounds access, potentially leading to memory corruption or unexpected behavior.
The fix involves adding a bounds check using ARRAY_SIZE() to ensure eng_id is within valid limits before it is used as an index. Additionally, casting to unsigned rejects negative values, preventing invalid indexing.
How can this vulnerability impact me? :
Out-of-bounds memory access vulnerabilities like this can lead to memory corruption, crashes, or potentially allow an attacker to execute arbitrary code or cause denial of service. In this case, if the Linux kernel's AMD display driver accesses memory beyond the intended array bounds, it could destabilize the system or be exploited by malicious actors.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed by adding a bounds check before using the eng_id as an index into the stream_enc_regs[] array in the Linux kernel's AMD GPU display driver code.
Immediate mitigation steps include updating the Linux kernel to a version that includes this fix, which ensures that eng_id is properly checked against the array size to prevent out-of-bounds access.