dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10410

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 MDM9206, MDM9607, MDM9615, MDM9625, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, 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 835, SD 845, SD 850, and SDX20, buffer overflow vulnerability in RTP during Volte call.

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 RTP (Real-time Transport Protocol) implementation within the Qualcomm baseband/modem firmware, specifically triggered during VoLTE (Voice over LTE) calls. This memory corruption vulnerability in the modem processor could allow remote code execution via specially crafted RTP packets, as the CVSS 9.8 indicates trivial network exploitation with complete system compromise.

MitigationApply Android security patch level 2018-04-05 or later from the device OEM, which includes the Qualcomm baseband firmware fix. Users of affected devices should check for and install available system updates immediately.

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
Mdm9615 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

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. Check baseband firmware version
    Navigate to Settings > About Phone > Baseband (or Modem) version on the Android device. Record the full version string shown.
    Affected if The baseband version corresponds to any of these affected modem models: Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, or Mdm9650. Note that all firmware versions of these modems are affected.
  2. Identify the modem model
    Examine the baseband version string or modem identification information. The modem model number (such as Mdm9206 or Mdm9607) is typically embedded in the baseband firmware identifier.
    Affected if The modem model number matches any of: Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, or Mdm9650.
  3. Verify VoLTE is enabled
    Navigate to Settings > Mobile Network (or Cellular) > VoLTE (or Voice over LTE). Check whether the VoLTE toggle is turned ON or OFF.
    Affected if VoLTE is enabled on the device. The vulnerability is triggered specifically during VoLTE calls, so VoLTE must be active for exploitation to be possible.
  4. Check Android security patch level
    Navigate to Settings > About Phone > Android security patch level. Note the date shown (format is typically YYYY-MM-DD).
    Affected if The security patch level is earlier than 2018-04-05, indicating the Qualcomm baseband fix has not been applied.

The device is affected if it contains any of the listed Qualcomm modem models (Mdm9206, Mdm9607, Mdm9615, Mdm9625, Mdm9635m, Mdm9640, Mdm9645, or Mdm9650), has VoLTE enabled, and the Android security patch level is earlier than 2018-04-05.

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 from the device OEM, which includes the Qualcomm baseband firmware fix. Users of affected devices should check for and install available system updates immediately.

Recommended fix High confidence

Android 2018-04-05 security patch level or later

  1. Ensure the device is updated to the Android 2018-04-05 security patch level or later. This can be done by checking for system updates in Settings > System > Security & privacy > Update security patch or Settings > About phone > Security patch level.
  2. If the device manufacturer has released a specific firmware update addressing this CVE, apply that update through the manufacturer's update mechanism.
  3. For enterprise or embedded deployments, verify the security patch level by checking the 'ro.build.version.security_patch' system property.

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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