Kernel memory overflow via misread CSL field
Published Apr 16, 2020 · Updated Aug 5, 2024
Kernel memory corruption in Qualcomm Snapdragon SDA845, SDM845, and SM8150 allows local users to trigger a memory overflow. The kernel reads the CSL-defined reserved field as uint16 rather than uint32, misinterpreting its four-byte value and overflowing memory. Exploitation requires local low-privileged access to an affected device and can expose or corrupt kernel memory or crash the device.
Summary
What happened
Kernel memory corruption in Qualcomm Snapdragon SDA845, SDM845, and SM8150 allows local users to trigger a memory overflow. The kernel reads the CSL-defined reserved field as uint16 rather than uint32, misinterpreting its four-byte value and overflowing memory. Exploitation requires local low-privileged access to an affected device and can expose or corrupt kernel memory or crash the device.
The record
- CVE
- CVE-2019-14105
- Published
- Apr 16, 2020
- Updated
- Aug 5, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=SDA845, SDM845, SM8150
What conditions does exploitation require?
What is affected?
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