drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
Summary
| CVE | CVE-2026-53293 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-26 20:17:22 UTC |
| Updated | 2026-07-08 03:53:12 UTC |
| 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) |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.001680000 probability, percentile 0.064670000 (date 2026-07-04)
Problem Types: CWE-667
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 8361e3f7882876d98ba98cae0d3149450dd80912 8c4254c8f5836e77ae83e7fc037f02b69f7a0977 git | Not specified |
| CNA | Linux | Linux | affected 9e823f307074c0f82b5f6044943b0086e3079bed 61957c2e467b39b528a290016367d32a433fa846 git | Not specified |
| CNA | Linux | Linux | affected 9e823f307074c0f82b5f6044943b0086e3079bed a31c3feb54b15a90232e497ad0e27e8a82052d8d git | Not specified |
| CNA | Linux | Linux | affected 9e823f307074c0f82b5f6044943b0086e3079bed 5c29d20470d4566d1b68df57097d642d01f8b427 git | Not specified |
| CNA | Linux | Linux | affected 9e823f307074c0f82b5f6044943b0086e3079bed 0ef196a208385b7d7da79f411c161b04e97283e2 git | Not specified |
| CNA | Linux | Linux | affected 17a98c942cb106ec08564e8f43b5470a4dd5d3f6 git | Not specified |
| CNA | Linux | Linux | affected 9a98563345697bdb1d3410ff428473b2e781f4db git | Not specified |
| CNA | Linux | Linux | affected 6.6.55 6.6.141 semver | Not specified |
| CNA | Linux | Linux | affected 6.10.14 6.11 semver | Not specified |
| CNA | Linux | Linux | affected 6.11.3 6.12 semver | Not specified |
| CNA | Linux | Linux | affected 6.12 | Not specified |
| CNA | Linux | Linux | unaffected 6.12 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.141 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.91 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.33 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0.10 7.0.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/5c29d20470d4566d1b68df57097d642d01f8b427 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/a31c3feb54b15a90232e497ad0e27e8a82052d8d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/0ef196a208385b7d7da79f411c161b04e97283e2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/8c4254c8f5836e77ae83e7fc037f02b69f7a0977 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/61957c2e467b39b528a290016367d32a433fa846 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.