CVE-2016-5349 json
The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Q…
published 2017-04-06 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6300
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS.
Patch / fix
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Qualcomm, Inc. Qualcomm Snapdragon 800, 600, 400, 200
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
codeaurora.org
/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cve
issue-tracking, patch, third-party-advisory
-
source.android.com
/security/bulletin/2017-04-01
vendor-advisory
-
qualcomm.com
/company/product-security/security-advisories
vendor-advisory
-
securityfocus.com
/bid/97364
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038201
vdb-entry
Sources
- CVE List CVE-2016-5349
- NVD CVE-2016-5349
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.