Kernel compromise via failed GPU buffer unmap
Published May 6, 2024 · Updated Aug 15, 2024
Use-after-free in Qualcomm Graphics Linux allows local users to corrupt memory through failed IOMMU unmapping of a GPU buffer. The KGSL driver releases or reuses buffer backing memory after an unmap failure leaves the GPU mapping intact. Local access to GPU buffer operations is required, and exploitation grants control over the affected kernel graphics component.
Summary
What happened
Use-after-free in Qualcomm Graphics Linux allows local users to corrupt memory through failed IOMMU unmapping of a GPU buffer. The KGSL driver releases or reuses buffer backing memory after an unmap failure leaves the GPU mapping intact. Local access to GPU buffer operations is required, and exploitation grants control over the affected kernel graphics component.
The record
- CVE
- CVE-2024-21471
- Published
- May 6, 2024
- Updated
- Aug 15, 2024
- Vendor
- Qualcomm
- Product
- Robotics RB3 Platform Firmware
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 15, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
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.
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