Local memory corruption via unmapped GPU VBO
Published Aug 5, 2024 · Updated Aug 15, 2024
Use-after-free in Qualcomm Snapdragon Graphics Linux allows local users to corrupt memory through an improperly unmapped GPU VBO. The GPU SMMU fails to unmap memory mapped in a video buffer object, leaving a stale allocation accessible after its lifetime ends. Local access requires no prior privileges or user interaction; Qualcomm has not published the trigger or a more specific consequence beyond memory corruption.
Summary
What happened
Use-after-free in Qualcomm Snapdragon Graphics Linux allows local users to corrupt memory through an improperly unmapped GPU VBO. The GPU SMMU fails to unmap memory mapped in a video buffer object, leaving a stale allocation accessible after its lifetime ends. Local access requires no prior privileges or user interaction; Qualcomm has not published the trigger or a more specific consequence beyond memory corruption.
The record
- CVE
- CVE-2024-23381
- Published
- Aug 5, 2024
- Updated
- Aug 15, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 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.
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