Answer in brief
CVE-2026-53293 records a Medium severity (CVSS 5.5) vulnerability in drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8361e3f7882876d98ba98cae0d3149450dd80912 <8c4254c8f5836e77ae83e7fc037f02b69f7a0977 || >=9e823f307074c0f82b5f6044943b0086e3079bed <61957c2e467b39b528a290016367d32a433fa846 || >=9e823f307074c0f82b5f6044943b0086e3079bed <a31c3feb54b15a90232e497ad0e27e8a82052d8d || >=9e823f307074c0f82b5f6044943b0086e3079bed <5c29d20470d4566d1b68df57097d642d01f8b427 || >=9e823f307074c0f82b5f6044943b0086e3079bed <0ef196a208385b7d7da79f411c161b04e97283e2 || 17a98c942cb106ec08564e8f43b5470a4dd5d3f6 || 9a98563345697bdb1d3410ff428473b2e781f4db || >=6.6.55 <6.6.141 || >=6.10.14 <6.11 || >=6.11.3 <6.12 | 8c4254c8f5836e77ae83e7fc037f02b69f7a0977, 61957c2e467b39b528a290016367d32a433fa846, a31c3feb54b15a90232e497ad0e27e8a82052d8d, 5c29d20470d4566d1b68df57097d642d01f8b427, 0ef196a208385b7d7da79f411c161b04e97283e2, 6.6.141, 6.11, 6.12 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
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)
Quoted source text, attributed separately from HOL analysis.