CVEvulnerability
CVE-2026-53293
5.5 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-06-26
- Last modified
- 2026-07-08
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- 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 configurations
• linux linux kernel (>= 6.6.55 < 6.6.141)
• 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 7.1
Related
Weakness · CWE (1)
- CWE-667 Improper Locking weakness
References
- https://git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2 Patch
- https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427 Patch
- https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846 Patch
- https://git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977 Patch
- https://git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8d Patch