dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10502

CRITICAL · 9.8 CVSS v3.0 Published 2018-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
While generating trusted application id, An integer overflow can occur giving the trusted application an invalid identity in Snapdragon Mobile and Snapdragon Wear in versions MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835 and SDA660.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An integer overflow vulnerability exists in the trusted application ID generation logic within Qualcomm Snapdragon processors (MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SDA660). This flaw allows a trusted application to receive an invalid identity, potentially enabling privilege escalation or arbitrary code execution within the Trusted Execution Environment (TEE).

MitigationApply OEM-provided firmware updates from Qualcomm to address the integer overflow in the TEE trusted application ID generation. This is a hardware/firmware-level vulnerability requiring processor microcode or secure OS updates from device manufacturers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 835 FirmwareOperating system
Affected:all versions
Sda660 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the processor model
    On Android devices, run 'getprop ro.hardware' or check /proc/cpuinfo to identify the Qualcomm Snapdragon chipset model (e.g., MDM9206, MDM9607, SD 835, SDA660)
    Affected if The identified model matches any of: MDM9206, MDM9607, MDM9650, SD 210, SD 212, SD 205, SD 835, or SDA660
  2. Check if TEE/TrustZone is enabled
    On Android, run 'getprop ro.tee' or check /d/tee/ directory exists in debugfs. The vulnerability exists in the TEE trusted application ID generation logic, so a functioning TEE is required for this flaw to be exploitable.
    Affected if TEE (Trusted Execution Environment) or TrustZone is present and active on the device
  3. Retrieve the baseband processor firmware version
    On Android, run 'getprop gsm.version.baseband' or check 'AT+VER' via terminal to get the baseband firmware version associated with the MDM chipset
    Affected if The firmware version cannot be determined or the device uses any of the affected Qualcomm firmware variants listed
  4. Determine the secure OS version within TEE
    Check /d/tee/ or /sys/kernel/debug/tee/ for TEE (QSEE) information. On some devices, 'dmesg | grep QSEE' may reveal secure OS version details. This vulnerability exists in the trusted application ID generation within the TEE.
    Affected if The device implements QSEE (Qualcomm Secure Execution Environment) or similar TEE and the version information indicates unpatched firmware

A user is affected if their device contains any of the listed Qualcomm Snapdragon processors (MDM9206, MDM9607, MDM9650, SD 210/SD 212/SD 205, SD 835, SDA660) and the TEE is enabled, as the integer overflow exists in all firmware versions of these chipsets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply OEM-provided firmware updates from Qualcomm to address the integer overflow in the TEE trusted application ID generation. This is a hardware/firmware-level vulnerability requiring processor microcode or secure OS updates from device manufacturers.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10502 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10502 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data