Memory corruption via Speaker Protection parameter handling
Published Jan 21, 2021 · Updated Aug 4, 2024
Snapdragon audio-driver memory corruption allows local users to trigger a double free or invalid access while reading Speaker Protection parameters. The audio driver mishandles memory ownership while reading those parameters, allowing the same allocation to be freed twice or an invalid address to be accessed. Exploitation requires local low-privileged access; Qualcomm has not disclosed whether the corruption causes a crash, code execution, or data exposure.
Summary
What happened
Snapdragon audio-driver memory corruption allows local users to trigger a double free or invalid access while reading Speaker Protection parameters. The audio driver mishandles memory ownership while reading those parameters, allowing the same allocation to be freed twice or an invalid address to be accessed. Exploitation requires local low-privileged access; Qualcomm has not disclosed whether the corruption causes a crash, code execution, or data exposure.
The record
- CVE
- CVE-2020-11217
- Published
- Jan 21, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2021CVE 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.
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