Kernel memory corruption via stale VBO mappings
Published Aug 5, 2024 · Updated Aug 16, 2024
Use-after-free in Qualcomm Snapdragon Graphics Linux firmware allows local users to corrupt kernel memory through concurrent VBO operations. The KGSL VBO bind and reclaim paths can free mapped pages through the shrinker while stale GPU SMMU mappings remain reachable. A local process needs no prior privilege or user interaction; the resulting kernel-memory corruption can expose or alter data or crash the device.
Summary
What happened
Use-after-free in Qualcomm Snapdragon Graphics Linux firmware allows local users to corrupt kernel memory through concurrent VBO operations. The KGSL VBO bind and reclaim paths can free mapped pages through the shrinker while stale GPU SMMU mappings remain reachable. A local process needs no prior privilege or user interaction; the resulting kernel-memory corruption can expose or alter data or crash the device.
The record
- CVE
- CVE-2024-23384
- Published
- Aug 5, 2024
- Updated
- Aug 16, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 16, 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