Kernel memory corruption via mapping double free
Published Jun 22, 2020 · Updated Aug 4, 2024
Double free in Qualcomm Snapdragon DSP services on SM8150 allows local users to corrupt kernel memory through a kernel mapping operation. The mapping path frees the same allocation twice because it lacks a memory-protection mechanism; Qualcomm has not published the responsible function or input sequence. Low-privileged local access is required, and successful exploitation can compromise confidentiality, integrity, and availability within the existing security scope.
Summary
What happened
Double free in Qualcomm Snapdragon DSP services on SM8150 allows local users to corrupt kernel memory through a kernel mapping operation. The mapping path frees the same allocation twice because it lacks a memory-protection mechanism; Qualcomm has not published the responsible function or input sequence. Low-privileged local access is required, and successful exploitation can compromise confidentiality, integrity, and availability within the existing security scope.
The record
- CVE
- CVE-2020-3613
- Published
- Jun 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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