EUVD-2026-39898
GHSA-qxgc-w63m-xvqr
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Local ioctl access requires low privilege (DRM group); no confidentiality or integrity impact; kernel deadlock produces high availability loss.
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Lifecycle Timeline
5DescriptionNVD
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
There were multiple issues in that code.
First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock.
Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock.
Then we used down_read_trylock() instead of waiting for the reset to finish.
(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)
AnalysisAI
Improper locking in the Linux kernel's amdgpu DRM driver allows a local low-privileged user to trigger a kernel deadlock or system crash via the AMDGPU_INFO_READ_MMR_REG ioctl. Three distinct concurrency defects exist: inverted lock ordering between the reset semaphore and mm_lock (permitting copy_to_user() under lock), memory allocation while holding the reset semaphore, and use of down_read_trylock() where a blocking wait is required. …
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 | Exploitation requires: (1) a system with an AMD GPU installed and the amdgpu kernel module loaded; (2) local user access with permission to open the DRM device node (/dev/dri/renderD* or /dev/dri/card*), which typically requires membership in the 'video' or 'render' OS group, or equivalent CAP_SYS_ADMIN; (3) the kernel version must fall within the affected stable branch ranges listed above. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Real-world risk is moderate-to-low despite the CVSS 5.5 score. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A local user with access to the AMD GPU render node (e.g., a member of the 'render' group on a shared workstation or an unprivileged VM with GPU passthrough) issues a series of AMDGPU_INFO_READ_MMR_REG ioctl calls timed to coincide with a concurrent GPU reset event, triggering the inverted lock ordering or the allocation-under-semaphore path. The kernel deadlocks or panics, taking the entire system offline. … |
| Remediation | The primary remediation is upgrading to a patched Linux kernel version: 6.6.141, 6.12.91, 6.18.33, 7.0.10, or 7.1 (or later), as provided by the upstream stable tree at https://git.kernel.org/stable/. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-667 – Improper Locking
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today