dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10425

CRITICAL · 9.8 CVSS v3.0 Published 2018-04-18
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
In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, and SD 835, if GPT listener response is passed a large buffer offset, a buffer overflow occurs.

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

Buffer overflow vulnerability in the GPT (GUID Partition Table) listener component of multiple Qualcomm Snapdragon chipset variants (MDM9206, SD 210/212/205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, SD 835). The overflow occurs when the GPT listener response is passed a large buffer offset, potentially allowing arbitrary code execution.

MitigationApply Android security patch level 2018-04-05 or later to affected devices, or obtain and deploy vendor-specific firmware updates from device manufacturers for the affected Snapdragon chipsets.

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
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 FirmwareOperating system
Affected:all versions
Sd 400 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 FirmwareOperating system
Affected:all versions
Sd 425 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 Snapdragon chipset model in the device
    Check the device specifications or use system information commands (such as 'cat /proc/cpuinfo' on Android, or check bootloader/bandbase firmware identifiers) to confirm the exact Snapdragon variant
    Affected if The device uses any of these affected chipsets: MDM9206, SD 210, SD 212, SD 205, SD 400, SD 410, SD 412, SD 425, SD 430, SD 450, SD 615/16/415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 820A, or SD 835
  2. Check the baseband or firmware version
    Retrieve the baseband firmware version from the device (for example, using 'AT+CGMR' or through Android's 'Settings > About Phone > Baseband version' or 'ril.baseband.version' system property)
    Affected if The firmware version predates the 2018-04-05 Android security patch level or the vendor-specific patch for this CVE
  3. Verify the Android security patch level
    On Android devices, check 'Settings > About Phone > Android security patch level' or run 'getprop ro.build.version.security_patch' to see the installed patch date
    Affected if The security patch level is earlier than 2018-04-05
  4. Confirm GPT listener accessibility
    Determine whether the GPT listener component is exposed or accessible on the device. This may require checking device configuration, reviewing baseband logs, or using vendor diagnostic tools that can query the GPT listener status
    Affected if The GPT listener is enabled and accessible (which is the default state for affected firmware, since the vulnerability exists in the component itself)

A device is affected if it contains any of the listed Snapdragon chipset variants AND runs firmware or Android security patch levels predating the 2018-04-05 update.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android security patch level 2018-04-05 or later to affected devices, or obtain and deploy vendor-specific firmware updates from device manufacturers for the affected Snapdragon chipsets.

Recommended fix Moderate confidence

Android security patch level 2018-04-05 or later

  1. 1. Apply the Android security patch level released on or after April 5, 2018 to the affected device.
  2. 2. Verify the device is running a supported Android version with the 2018-04-05 or later security update applied.
  3. 3. Check the device manufacturer's documentation to confirm the security update includes the fix for CVE-2016-10425 (Qualcomm Snapdragon buffer overflow in GPT listener).
  4. 4. If the device cannot receive official security updates, consider replacing with a newer device or contact the device vendor for custom firmware updates.
Caveat Devices that no longer receive security updates from the manufacturer may need to be replaced; applying major OS updates may affect legacy application compatibility

Generated from the published advisory — verify against the referenced sources before acting.

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-10425 — 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-10425 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