VDB

CVE-2016-5349

CVE-2016-5349 PUBLISHED

Reported by qualcomm · Published April 6, 2017

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
androidgoogle7.1.1

Affected products

VendorProductVersions
Qualcomm, Inc.Qualcomm Snapdragon 800, 600, 400, 200All Android releases from CAF using the Linux kernel.
Qualcomm, Inc.Qualcomm Snapdragon 800, 600, 400, 200*

Timeline

  • Apr 4, 2017 CVE Published
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Jun 1, 2026 Security Advisory
  • Oct 8, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-5349
vulnetix vdb fixes CVE-2016-5349

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-5349/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_CONFIRM
  • x_refsource_CONFIRM
  • 97364 vdb-entryx_refsource_BID
  • x_refsource_CONFIRM
  • 1038201 vdb-entryx_refsource_SECTRACK
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›