Kernel code execution via DRM handle race
Published Jun 25, 2026 · Updated Jun 25, 2026
A race condition in Linux Kernel 6.18.32 through 6.18.35 and 7.0.9 through 7.0.12 allows local users to execute code in kernel mode. The gem_change_handle path confuses new and old handles, replaces the wrong IDR slot, and lets a concurrent gem_close steal the object's inherited reference. A low-privileged process needs access to a DRM render device and must race GEM_CHANGE_HANDLE against GEM_CLOSE; the resulting dangling object permits kernel memory corruption or a kernel crash.
Summary
What happened
A race condition in Linux Kernel 6.18.32 through 6.18.35 and 7.0.9 through 7.0.12 allows local users to execute code in kernel mode. The gem_change_handle path confuses new and old handles, replaces the wrong IDR slot, and lets a concurrent gem_close steal the object's inherited reference. A low-privileged process needs access to a DRM render device and must race GEM_CHANGE_HANDLE against GEM_CLOSE; the resulting dangling object permits kernel memory corruption or a kernel crash.
The record
- CVE
- CVE-2026-53145
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-367, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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=0dfa42cfe4dbe114533480503934f43e33c1e83d
- Affected versionversion=318b995cffcfcaa69a234d28123a3f4ae186a9df
- Affected versionversion=38f12d0e10d83b66fa1466400d876a3a8da31542
- Affected versionversion=5e28b7b94408897e41c63477aabc9e1db439bc8c <1a4f03d22fb655e5f192244fb2c87d8066fcfca2
- Affected versionversion=6.18.32 <6.18.36
- Affected versionversion=61bd96d3e5472c253f9c1ab77608f0c8aaa9d025 <1d9b93df7fc768228906e24220591ec1cddad391
- Affected versionversion=672464dd53231509c9c771110798c56d4660e19e <c0639ede2f24ac224b2079cd35ecd5fd8ad4e3cd
- Affected versionversion=7.0.9 <7.0.13
- Affected versionversion=cde2c9257cbe8463b9dcf7b1075177b72b5fd938
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