Local memory corruption via GNSS HAL use-after-free
Published Nov 4, 2024 · Updated Nov 16, 2024
Use-after-free memory corruption in Qualcomm Snapdragon GNSS HAL allows local users to alter memory during process initialization. Qualcomm has not published the freed object, initialization code path, or input that causes the stale reference to be used. Low-privileged local access is required without user interaction, and successful exploitation can compromise data and interrupt the affected HAL process.
Summary
What happened
Use-after-free memory corruption in Qualcomm Snapdragon GNSS HAL allows local users to alter memory during process initialization. Qualcomm has not published the freed object, initialization code path, or input that causes the stale reference to be used. Low-privileged local access is required without user interaction, and successful exploitation can compromise data and interrupt the affected HAL process.
The record
- CVE
- CVE-2024-38424
- Published
- Nov 4, 2024
- Updated
- Nov 16, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 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.
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