CVE-2026-53293
Published Jun 26, 2026
Modified Jun 30, 2026
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)
EPSS — Exploit Prediction
0.0017
Probability of exploitation
0.06%
Percentile rank
EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.
References
Other References
https://git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2
https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427
https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846
https://git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977
https://git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8d
Frequently Asked Questions
What is CVE-2026-53293? +
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)
How do I check if I'm vulnerable to CVE-2026-53293? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.