dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9216

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, MDM9625, MDM9635M, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 425, SD 430, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 808, and SD 810, improper handling of simultaneous interrupt in USB module during USB RESET and EP COMPLETE.

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

Vulnerability in Qualcomm Snapdragon USB module where simultaneous interrupts during USB RESET and EP COMPLETE operations are improperly handled, potentially allowing code execution or denial of service. Affects multiple Snapdragon mobile and wearable processors with Android before the 2018-04-05 security patch level.

MitigationApply Android security patch level from April 5, 2018 or later; this is a firmware-level fix delivered through OEM security updates. Devices should be updated to the latest manufacturer security 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
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m 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

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 processor model
    Check device specifications or use 'getprop ro.hardware' or 'getprop ro.product.device' to identify the Qualcomm processor variant. Look for identifiers matching Mdm9206, Mdm9607, Mdm9625, Mdm9635m, Msm8909w, Sd210, Sd212, or Sd205.
    Affected if Device uses any of the listed affected Qualcomm processor models
  2. Check Android security patch level
    Navigate to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' to retrieve the installed patch level.
    Affected if Security patch level is earlier than 2018-04-05 or the field is empty/unavailable
  3. Verify USB functionality is present
    Confirm the device has USB capabilities by checking if /sys/class/android_usb or /dev/usb-ffs/adb exists, or simply verify the device has USB connectivity features.
    Affected if Device has active USB module (required for the vulnerability to be exploitable)
  4. Confirm firmware update status
    Check the baseband version via 'getprop gsm.version.baseband' or check for OEM software updates in Settings > System > Software Update.
    Affected if Baseband/firmware has not been updated by the OEM after April 5, 2018

A device is affected if it contains any of the listed Qualcomm processors and is running an Android security patch level earlier than April 5, 2018, as the vulnerability exists in the USB module firmware that was patched in that release.

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 from April 5, 2018 or later; this is a firmware-level fix delivered through OEM security updates. Devices should be updated to the latest manufacturer security patches.

Recommended fix Moderate confidence

Android security patch level 2018-04-05 or later (contact OEM for specific update)

  1. Check if your device manufacturer provides Android security updates
  2. Contact your device OEM (Original Equipment Manufacturer) to verify if a security patch level of 2018-04-05 or later is available for your specific device model
  3. If available, apply the latest Android security update through your device's system update mechanism
  4. If no update is available from your OEM, consider migrating to a newer device that receives regular security patches
  5. For embedded/IoT devices using these modems, contact the device vendor for firmware updates addressing this USB interrupt handling vulnerability
Caveat Older devices may have reached End-of-Life and no longer receive security updates from OEMs

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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