---
id: CVE-2026-53293
title: 'drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG'
summary: |-
  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. c…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 8361e3f7882876d98ba98cae0d3149450dd80912 <
    8c4254c8f5836e77ae83e7fc037f02b69f7a0977
  - >-
    Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed <
    61957c2e467b39b528a290016367d32a433fa846
  - >-
    Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed <
    a31c3feb54b15a90232e497ad0e27e8a82052d8d
  - >-
    Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed <
    5c29d20470d4566d1b68df57097d642d01f8b427
  - >-
    Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed <
    0ef196a208385b7d7da79f411c161b04e97283e2
  - Linux 17a98c942cb106ec08564e8f43b5470a4dd5d3f6
  - Linux 9a98563345697bdb1d3410ff428473b2e781f4db
  - Linux >= 6.6.55 < 6.6.141
  - Linux >= 6.10.14 < 6.11
  - Linux >= 6.11.3 < 6.12
  - Linux 6.12
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-06T16:25:39.230314Z'
published: '2026-06-26'
updated: '2026-11-06'
sourceUpdated: '2026-11-06T16:34:18.602Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-53293'
references:
  - url: 'https://git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977'
  - url: 'https://git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846'
  - url: 'https://git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8d'
  - url: 'https://git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427'
  - url: 'https://git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2'
tags:
  - cve.org
epss: 0.00125
epssPercentile: 0.02211
ingestedAt: '2026-11-06T16:57:43.252Z'
---

## Overview

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

- `Linux >= 8361e3f7882876d98ba98cae0d3149450dd80912 < 8c4254c8f5836e77ae83e7fc037f02b69f7a0977`
- `Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed < 61957c2e467b39b528a290016367d32a433fa846`
- `Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed < a31c3feb54b15a90232e497ad0e27e8a82052d8d`
- `Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed < 5c29d20470d4566d1b68df57097d642d01f8b427`
- `Linux >= 9e823f307074c0f82b5f6044943b0086e3079bed < 0ef196a208385b7d7da79f411c161b04e97283e2`
- `Linux 17a98c942cb106ec08564e8f43b5470a4dd5d3f6`
- `Linux 9a98563345697bdb1d3410ff428473b2e781f4db`
- `Linux >= 6.6.55 < 6.6.141`
- `Linux >= 6.10.14 < 6.11`
- `Linux >= 6.11.3 < 6.12`
- `Linux 6.12`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.