dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9186

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, MDM9650, 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 820A, SD 835, SD 845, and SD 850, in a PlayReady API function, a buffer over-read can occur.

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 over-read vulnerability exists in the PlayReady API function within the Qualcomm Snapdragon processor firmware on Android devices (Automobile, Mobile, and Wear variants). This memory access vulnerability allows reading beyond allocated buffer boundaries, potentially exposing sensitive data or enabling arbitrary code execution.

MitigationApply Android security patches from April 5, 2018 or later; ensure affected devices (MDM9206, MDM9650, MSM8909W, SD series chipsets listed) receive regular firmware and OS 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
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w 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 Qualcomm chipset model
    Check device specifications or use AT commands (like AT+CGMM or AT+QCFG) to query the modem/processor model. On Android, also check /proc/cpuinfo or Settings > About Phone > Baseband.
    Affected if The chipset model is one of: Mdm9206, Mdm9650, Msm8909w, Sd 210, Sd 212, Sd 205, Sd 400, or Sd 410.
  2. Check the baseband firmware version
    On Android, go to Settings > About Phone > Baseband version, or use *#*#INFO#*#* (*#*#4636#*#*) to view detailed radio and firmware information.
    Affected if The firmware version is any version on the affected chipsets listed (all versions are vulnerable).
  3. Verify Android security patch level
    On Android, go to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell.
    Affected if The security patch level is earlier than April 5, 2018.
  4. Confirm PlayReady is in use
    Check if the device uses PlayReady DRM for media playback. This can be verified through app permissions, DRM logs, or by inspecting installed media applications that require DRM protection.
    Affected if PlayReady DRM functionality is present and active on the device.

The device is likely affected if it contains one of the listed Qualcomm Snapdragon chipsets (Mdm9206, Mdm9650, Msm8909w, SD 210/212/205/400/410) and has not received the April 5, 2018 or later Android security patch.

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 patches from April 5, 2018 or later; ensure affected devices (MDM9206, MDM9650, MSM8909W, SD series chipsets listed) receive regular firmware and OS security updates.

Recommended fix High confidence

Android security patch level May 2018 or later (2018-04-05 or later)

  1. Check current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  2. If the security patch level is April 5, 2018 or earlier, apply the latest available Android security update from the device manufacturer
  3. Verify after update that the security patch level shows May 2018 or later
Caveat Ensure device manufacturer provides ongoing security updates for your specific device model; some 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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