Kernel memory corruption via oversized GPU allocation
Published Jul 1, 2024 · Updated Aug 1, 2024
Memory corruption in Qualcomm Snapdragon display drivers allows local users to corrupt kernel memory through a crafted GPU allocation IOCTL. The gpumem_alloc_vbo_entry function fails to reject an oversized VBO allocation size before GPU address-range arithmetic, allowing the range endpoint to wrap. Access to the KGSL GPU device is required; successful exploitation can compromise kernel confidentiality, integrity, and availability.
Summary
What happened
Memory corruption in Qualcomm Snapdragon display drivers allows local users to corrupt kernel memory through a crafted GPU allocation IOCTL. The gpumem_alloc_vbo_entry function fails to reject an oversized VBO allocation size before GPU address-range arithmetic, allowing the range endpoint to wrap. Access to the KGSL GPU device is required; successful exploitation can compromise kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-23372
- Published
- Jul 1, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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.
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