dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9136

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, MDM9640, MDM9650, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 600, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, and SDX20, in pre-auth request, Host driver uses FT IEs sent by the supplicant. A buffer overflow may occur if FT IEs sent by the supplicant are larger than the expected value.

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 exists in the Host driver of Qualcomm Snapdragon chipsets where FT IEs (Fast Transition Information Elements) sent by the supplicant are used without proper bounds checking. If the FT IEs exceed the expected size, a buffer overflow occurs in pre-authentication requests, potentially allowing remote code execution.

MitigationApply the vendor security patch (April 2018 or later security patch level) to affected Android devices with vulnerable Qualcomm Snapdragon or Snapdragon Wear chipsets.

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
Mdm9640 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 425 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 or use diagnostic tools (such as AT commands or firmware identification utilities) to determine the exact Qualcomm Snapdragon or Snapdragon Wear chipset model number
    Affected if The chipset model is one of: Mdm9206, Mdm9607, Mdm9640, Mdm9650, Sd 210, Sd 212, Sd 205, or Sd 425
  2. Check the firmware version
    Retrieve the firmware version from the chipset using vendor-specific diagnostic tools or AT command interfaces (for example, AT+QVERSION or similar). Compare the firmware version against the affected version range
    Affected if The firmware version is any version (all versions are affected according to the advisory)
  3. Determine if Wi-Fi is enabled
    Check the device Wi-Fi status through the operating system network settings or wireless driver interface. Confirm that Wi-Fi functionality is active
    Affected if Wi-Fi is enabled and the device is capable of transmitting or receiving wireless pre-authentication requests
  4. Check if 802.11r Fast Transition is configured
    Inspect the wireless configuration settings or supplicant configuration (wpa_supplicant.conf) for the presence of 802.11r (FT) or Fast Transition parameters and mobility domain configurations
    Affected if 802.11r Fast Transition is enabled and the device processes FT IEs in pre-authentication requests

The device is affected if it uses any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9640, Mdm9650, Sd 210, Sd 212, Sd 205, or Sd 425) with any firmware version and has Wi-Fi with 802.11r Fast Transition enabled.

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 vendor security patch (April 2018 or later security patch level) to affected Android devices with vulnerable Qualcomm Snapdragon or Snapdragon Wear chipsets.

Recommended fix High confidence

Android Security Patch Level April 2018 or later (contact device OEM for specific firmware版本)

  1. 1. Identify the affected device model and verify it contains one of the affected Qualcomm Snapdragon or MDM chipsets (MDM9206, MDM9607, MDM9640, MDM9650, SD 210, SD 212, SD 205, SD 425, or others listed in the full Android bulletin)
  2. 2. Check the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  3. 3. If the security patch level is earlier than April 5, 2018, the device is vulnerable
  4. 4. Contact the device manufacturer (OEM) to obtain an update to Android security patch level April 2018 or later
  5. 5. Apply the manufacturer-provided system update that includes the April 2018 Android Security Bulletin fixes
  6. 6. After updating, verify the security patch level shows April 2018 or later
Caveat Firmware-level update; verify device is on manufacturer-supported update path; older devices may no longer receive patches

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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