What’s Vulnerable › Vulnerabilities

CVE-2026-53293: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG

• Severity: medium (CVSS 5.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.1% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-06-26 · updated 2026-07-08
• Weakness: CWE-667

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)

Affected products

• Linux kernel: from 6.6.55 before 6.6.141; from 6.10.14 before 6.11; from 6.11.3 before 6.12.91; from 6.13 before 6.18.33; from 6.19 before 7.0.10; 7.1-rc1 — fixed in 6.11, 6.12.91, 6.18.33, 6.6.141, 7.0.10

How to fix

Upgrade to a fixed version: Linux kernel 6.11, 6.12.91, 6.18.33, 6.6.141. Check the vendor advisory for mitigations.

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

Get alerted when CVE-2026-53293 or the next vulnerability affects your stack