QSEE crash via speculative device-memory fetches
Published Nov 26, 2024 · Updated Nov 26, 2024
Improper access control in QSEE on Qualcomm Snapdragon Mobile chipsets allows local users to crash the trusted execution environment. QSEE speculatively fetches instructions from device-memory regions even though those regions are not executable, producing a fatal execution error. Exploitation requires local access to an affected chipset, and the disclosed behavior interrupts QSEE; no trigger details are public.
Summary
What happened
Improper access control in QSEE on Qualcomm Snapdragon Mobile chipsets allows local users to crash the trusted execution environment. QSEE speculatively fetches instructions from device-memory regions even though those regions are not executable, producing a fatal execution error. Exploitation requires local access to an affected chipset, and the disclosed behavior interrupts QSEE; no trigger details are public.
The record
- CVE
- CVE-2016-10408
- Published
- Nov 26, 2024
- Updated
- Nov 26, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon 820 Firmware
- Classifications
- CWE-284, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 26, 2024CVE publishedPublication date reported by the CVE source.
- Nov 26, 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.
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