EUVD-2026-80414
GHSA-hf6p-44h5-hp6x
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local GPU-submission access (AV:L/PR:L); trigger depends on partition/ring state (AC:H); realistic impact is kernel crash (A:H) with possible limited adjacent-memory disclosure (C:L), not reliable integrity compromise.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
5DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: clamp the isolation index for rings outside a partition
adev->isolation[] has one slot per partition, but a ring that is not assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing the array with it is out of bounds. SDMA submissions hit this on both the isolation enforcement and the VM flush path and trip UBSAN.
Fall back to the first slot the way the cleaner shader path already does, and stop taking the address before the ring type check that makes it relevant.
AnalysisAI
An out-of-bounds array access in the Linux kernel's AMDGPU driver (drm/amdgpu) lets a local user who can submit GPU work trigger a kernel fault when a ring that was never assigned to a compute partition (AMDGPU_XCP_NO_PARTITION, i.e. ~0) is used on the SDMA isolation-enforcement or VM-flush paths. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires LOCAL access to an affected AMD GPU on a Linux host running the amdgpu driver, and the ability to submit GPU work (e.g. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | All exploitation signals point to LOCAL, not remote: the vendor CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8) requires local access and low privileges, and the description ('SDMA submissions hit this') confirms an on-host GPU-command-submission path, so the AV:L is consistent with the text. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Apply the vendor patch by upgrading to Linux 6.18.51, 7.2.5 or 7.3-rc1 (or any later release containing the corresponding stable commits 964de255497ffd7cb8a86e405b8ac6d927e7e177, b30900566642ceb2c9e12b56c2afec28d0fd91a0 and 0bfb938182d1313e5cac32ae38dbaaa4eabe4af4, published at https://git.kernel.org/stable/c/964de255497ffd7cb8a86e405b8ac6d927e7e177). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Linux hosts with AMD GPUs and record their kernel versions, prioritising multi-user GPU compute nodes, AI/ML clusters, and virtual desktop hosts where partition isolation (AMDGPU_XCP) is enabled, and confirm whether unprivileged local users or tenant workloads can submit GPU work. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today