Local kernel compromise via premature fence release
Published Jan 23, 2024 · Updated Oct 3, 2024
Use-after-free in Linux kernel amdgpu before 6.4.12 allows local users to access a released fence during GPU command submission. amdgpu_cs_wait_all_fences calls dma_fence_put and then reads fence->error, allowing another execution context to reclaim the fence before that read. Exploitation requires low-privileged local access and an AMD GPU using amdgpu, with resulting kernel memory compromise or a system crash.
Summary
What happened
Use-after-free in Linux kernel amdgpu before 6.4.12 allows local users to access a released fence during GPU command submission. amdgpu_cs_wait_all_fences calls dma_fence_put and then reads fence->error, allowing another execution context to reclaim the fence before that read. Exploitation requires low-privileged local access and an AMD GPU using amdgpu, with resulting kernel memory compromise or a system crash.
The record
- CVE
- CVE-2023-51042
- Published
- Jan 23, 2024
- Updated
- Oct 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 23, 2024CVE publishedPublication date reported by the CVE source.
- Oct 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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