dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10485

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 Mobile and Snapdragon Wear IPQ4019, MDM9206, MDM9607, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 617, SD 650/52, SD 800, SD 808, SD 810, and SDX20, lack of proper bounds checking may lead to a buffer overflow.

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 · moderate confidence

A buffer overflow vulnerability exists in Qualcomm Snapdragon Mobile and Snapdragon Wear chipsets due to lack of proper bounds checking. This low-level firmware/baseband vulnerability affects multiple chipset models running Android with security patch levels before April 5, 2018, and could allow remote code execution or denial of service.

MitigationApply the April 2018 or later Android security patch level update from the device vendor. If the device is no longer supported, consider replacement with a currently-supported device receiving regular security updates.

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
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 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 Qualcomm modem model
    On the Android device, go to Settings > About Phone > Hardware Information or use the command 'getprop | grep persist.sys.modem' to retrieve the modem model identifier. Look for model numbers Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655.
    Affected if The device displays one of these modem model numbers in its hardware or baseband information.
  2. Check the Android security patch level
    Navigate to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' in a terminal. This displays the installed security update date.
    Affected if The security patch level is dated before April 5, 2018.
  3. Verify the baseband firmware version
    Access Settings > About Phone > Baseband version, or execute 'getprop gsm.version.baseband' in a terminal. This shows the specific firmware version running on the modem.
    Affected if The baseband version corresponds to firmware for any of the affected Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655 chipsets.

The device is affected if it contains any of the listed Qualcomm modem models and is running an Android security patch level predating April 5, 2018.

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 the April 2018 or later Android security patch level update from the device vendor. If the device is no longer supported, consider replacement with a currently-supported device receiving regular security updates.

Recommended fix Moderate confidence

Android security patch level 2018-04-05 or later

  1. 1. Identify the device manufacturer and model containing the affected Qualcomm Snapdragon modem (Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, or Mdm9655)
  2. 2. Contact the device manufacturer or mobile carrier to obtain firmware/modem updates
  3. 3. Apply the Android security patch level released April 5, 2018 or later, which contains the fix for this vulnerability
  4. 4. Verify the device is running the updated firmware/modem software by checking the Android security patch level in Settings > About Phone > Software Information
Caveat Firmware updates may require carrier support and may not be available for all devices; older devices may not receive updates

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10485 — 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-10485 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