Memory corruption via HGSL context-create use-after-free
Published Mar 4, 2024 · Updated Aug 26, 2024
Use-after-free in Qualcomm Snapdragon HGSL firmware allows local users to corrupt memory through an IOCTL context-create request. The HGSL context-create path accesses memory after its lifetime ends, but Qualcomm has not identified the freed object or triggering sequence publicly. A local user needs no prior privileges or user interaction, and successful exploitation can compromise data and interrupt device operation.
Summary
What happened
Use-after-free in Qualcomm Snapdragon HGSL firmware allows local users to corrupt memory through an IOCTL context-create request. The HGSL context-create path accesses memory after its lifetime ends, but Qualcomm has not identified the freed object or triggering sequence publicly. A local user needs no prior privileges or user interaction, and successful exploitation can compromise data and interrupt device operation.
The record
- CVE
- CVE-2023-43546
- Published
- Mar 4, 2024
- Updated
- Aug 26, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 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