dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10412

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 Small Cell SoC, Snapdragon Mobile, and Snapdragon Wear FSM9055, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 600, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 800, SD 808, SD 810, SD 820, SD 835, and SDX20, an integer overflow leading to buffer overflow can potentially occur in a memory API function.

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

Integer overflow leading to buffer overflow in a memory API function in Qualcomm Snapdragon chipsets (FSM9055, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, MSM8909W, SD series, SDX20) used in Android devices before the 2018-04-05 security patch level. This is a memory corruption vulnerability that could allow remote code execution or privilege escalation.

MitigationApply the 2018-04-05 or later security patch level from device manufacturers, which includes the Qualcomm firmware fix. For embedded/IoT devices using these chipsets, obtain and deploy firmware updates from the respective device vendors.

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
Fsm9055 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w 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 chipset model
    Check the device specifications in Settings > About Phone, or run 'cat /proc/cpuinfo' to find the chipset/broadcom modem info. Also check Settings > About Phone > Baseband or Modem version.
    Affected if The chipset model is one of: FSM9055, MDM9206, MDM9607, MDM9615, MDM9635M, MDM9640, MDM9650, or MSM8909W
  2. Check the baseband/modem firmware version
    In Android Settings > About Phone > Baseband version, or run 'getprop ro.baseband' or 'getprop gsm.version.baseband' in ADB shell.
    Affected if The firmware version cannot be determined or is prior to the vendor fix (no specific version number provided in advisory)
  3. Check the Android security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' in ADB shell.
    Affected if The security patch level is earlier than 2018-04-05 (e.g., March 2018 or earlier)
  4. Verify if device manufacturer has released an update
    Check the device manufacturer support page or Settings > Software Update to see if a firmware update is available.
    Affected if No update is available from the device manufacturer that includes the 2018-04-05 security patch or later

The device is affected if it contains one of the listed Qualcomm chipsets and has a security patch level 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 the 2018-04-05 or later security patch level from device manufacturers, which includes the Qualcomm firmware fix. For embedded/IoT devices using these chipsets, obtain and deploy firmware updates from the respective device vendors.

Recommended fix High confidence
  1. Check current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  2. If the Security Patch Level is earlier than April 5, 2018, apply the available system update from the device manufacturer
  3. Contact the device manufacturer (OEM) if the update is not available and request the security patch
Caveat Device must be supported by OEM to receive the security update; older devices may not receive patches

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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