Sensitive data disclosure via null pointer dereference
Published Jan 8, 2020 · Updated Aug 6, 2024
Information disclosure in the Qualcomm Avtimer driver on Google Pixel and Pixel XL allows local users to read sensitive kernel data. The AF_MSM_IPC socket accept path dereferences a null address and exposes memory outside the calling application's permission boundary. Exploitation requires a local malicious application and prior compromise of a privileged process; the reported impact is limited to confidentiality.
Summary
What happened
Information disclosure in the Qualcomm Avtimer driver on Google Pixel and Pixel XL allows local users to read sensitive kernel data. The AF_MSM_IPC socket accept path dereferences a null address and exposes memory outside the calling application's permission boundary. Exploitation requires a local malicious application and prior compromise of a privileged process; the reported impact is limited to confidentiality.
The record
- CVE
- CVE-2016-5346
- Published
- Jan 8, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1533
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
- CVE-2016-5346 proof of conceptproof of concept · unverified
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