Bug 2493700 (CVE-2026-53293) - CVE-2026-53293 kernel: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
Summary: CVE-2026-53293 kernel: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
Keywords:
Status: NEW
Alias: CVE-2026-53293
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-26 21:01 UTC by OSIDB Bzimport
Modified: 2026-06-29 11:09 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-26 21:01:30 UTC
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)

Comment 1 Mauro Matteo Cascella 2026-06-29 11:02:16 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062617-CVE-2026-53293-e4ad@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.