dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2016-10441

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, MDM9650, 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, improper offset validation leads to buffer overflow in video parser.

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

A buffer overflow vulnerability in the video parser of Qualcomm Snapdragon processors allows remote code execution due to improper offset validation. This affects multiple Snapdragon and Snapdragon Wear chipsets across Android devices released before the April 2018 security patch level.

MitigationUpdate affected Android devices to the April 2018 security patch level (2018-04-05) or later, which contains the proper offset validation fix from Qualcomm. Contact device OEMs/vendors for availability of vendor-specific patches.

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 400 FirmwareOperating system
Affected:all versions
Sd 410 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 device chipset model
    Check the processor/chipset information using 'getprop ro.hardware' or by examining /proc/cpuinfo. Alternatively, check 'getprop ro.product.device' or 'getprop ro.product.name' to identify the device model, then cross-reference with the chipset documentation.
    Affected if The device uses any of these chipsets: Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410.
  2. Verify the Android security patch level
    Run 'getprop ro.build.version.security_patch' to retrieve the installed security patch date.
    Affected if The security patch level is earlier than 2018-04-05 (April 2018).
  3. Confirm the baseband firmware version
    Check the radio firmware version using 'getprop gsm.version.baseband' or 'getprop ro.radioversion'.
    Affected if The firmware version string corresponds to one of the affected chipsets listed in the CVE.
  4. Check for video parser usage
    This vulnerability resides in the video parser component. Any device that processes video content through the affected chipset parser could be triggerable. Confirm the device has video playback capability.
    Affected if The device has video playback functionality and uses an affected chipset with a pre-April-2018 patch level.

A device is affected if it contains any of the listed Qualcomm chipset models (Mdm9206, Mdm9607, Mdm9650, Sd 210, Sd 212, Sd 205, Sd 400, Sd 410) and has not received the April 2018 security patch level or later.

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

Update affected Android devices to the April 2018 security patch level (2018-04-05) or later, which contains the proper offset validation fix from Qualcomm. Contact device OEMs/vendors for availability of vendor-specific patches.

Recommended fix Moderate confidence

Android security patch level 2018-04-05 or later (or device manufacturer firmware update containing this patch)

  1. 1. Identify the current Android security patch level on the affected device by going to Settings > About Phone > Security Patch Level
  2. 2. If the security patch level is earlier than April 5, 2018, check for available system updates from the device manufacturer
  3. 3. Apply the latest Android system update that includes the 2018-04-05 security patch level or later
  4. 4. If no system update is available from the device manufacturer, contact the device manufacturer for a firmware update that addresses this vulnerability
  5. 5. As a temporary mitigation, avoid opening untrusted video files or using untrusted video applications until the patch is applied
Caveat Devices no longer receiving security updates from manufacturers may not have a patch available; older devices may not be upgradeable to the required security patch level

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
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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