Vulnerability 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 Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.6.55, < 6.6.141 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2Patch
- https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427Patch
- https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846Patch
- https://git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977Patch
- https://git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8dPatch
FAQ
What is CVE-2026-53293?
CVE-2026-53293 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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 semaph...
How severe is CVE-2026-53293?
CVE-2026-53293 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-53293?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.