Tracker / CVE-2026-53293
CVE-2026-53293
Medium 5.5
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)
Affected products and versions
| linux | linux_kernel |
|---|---|
| linux | linux_kernel · 6.10.14 → 6.11 |
| linux | linux_kernel · 6.11.3 → 6.12.91 |
| linux | linux_kernel · 6.13 → 6.18.33 |
| linux | linux_kernel · 6.19 → 7.0.10 |
| linux | linux_kernel · 6.6.55 → 6.6.141 |
Analysis
This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.