Local system hang via AMDGPU ioctl deadlock
Published Jun 26, 2026 · Updated Jun 26, 2026
Improper locking in the Linux Kernel AMDGPU driver allows local users to hang affected systems through AMDGPU_INFO_READ_MMR_REG. The ioctl path calls copy_to_user while holding mm_lock, allocates memory under the reset semaphore, and uses down_read_trylock instead of waiting for reset completion. Exploitation requires local access to an AMDGPU device and interrupts service by deadlocking kernel work without exposing or changing data.
Summary
What happened
Improper locking in the Linux Kernel AMDGPU driver allows local users to hang affected systems through AMDGPU_INFO_READ_MMR_REG. The ioctl path calls copy_to_user while holding mm_lock, allocates memory under the reset semaphore, and uses down_read_trylock instead of waiting for reset completion. Exploitation requires local access to an AMDGPU device and interrupts service by deadlocking kernel work without exposing or changing data.
The record
- CVE
- CVE-2026-53293
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-833, CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17a98c942cb106ec08564e8f43b5470a4dd5d3f6
- Affected versionversion=6.10.14 <6.11
- Affected versionversion=6.11.3 <6.12
- Affected versionversion=6.12
- Affected versionversion=6.6.55 <6.6.141
- Affected versionversion=8361e3f7882876d98ba98cae0d3149450dd80912 <8c4254c8f5836e77ae83e7fc037f02b69f7a0977
- Affected versionversion=9a98563345697bdb1d3410ff428473b2e781f4db
- Affected versionversion=9e823f307074c0f82b5f6044943b0086e3079bed <0ef196a208385b7d7da79f411c161b04e97283e2
- Affected versionversion=9e823f307074c0f82b5f6044943b0086e3079bed <5c29d20470d4566d1b68df57097d642d01f8b427
- Affected versionversion=9e823f307074c0f82b5f6044943b0086e3079bed <61957c2e467b39b528a290016367d32a433fa846
- Affected versionversion=9e823f307074c0f82b5f6044943b0086e3079bed <a31c3feb54b15a90232e497ad0e27e8a82052d8d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo