CVE-2026-53293
Analyzed Analyzed - Analysis Complete

AMDGPU Memory Access Vulnerability in Linux Kernel

Vulnerability report for CVE-2026-53293, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-26

Last updated on: 2026-07-08

Assigner: kernel.org

Description

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)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-26
Last Modified
2026-07-08
Generated
2026-07-17
AI Q&A
2026-06-26
EPSS Evaluated
2026-07-15
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 6.10.14 (inc) to 6.11 (exc)
linux linux_kernel 7.1
linux linux_kernel From 6.13 (inc) to 6.18.33 (exc)
linux linux_kernel From 6.19 (inc) to 7.0.10 (exc)
linux linux_kernel From 6.11.3 (inc) to 6.12.91 (exc)
linux linux_kernel From 6.6.55 (inc) to 6.6.141 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-667 The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's AMDGPU driver, specifically in the drm/amdgpu code related to AMDGPU_INFO_READ_MMR_REG.

The issues include incorrect ordering between the reset semaphore and the mm_lock, which caused functions like copy_to_user to be called while holding the lock.

Additionally, memory was allocated while holding the reset semaphore, which is a significant bug that can lead to deadlocks.

Finally, the code used down_read_trylock() instead of properly waiting for the reset to finish, which could cause synchronization problems.

Impact Analysis

This vulnerability can lead to system instability or deadlocks due to improper locking and memory allocation in the AMDGPU driver.

Such deadlocks or synchronization issues may cause the affected system to hang or crash, impacting availability and reliability.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53293. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart