dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2015-9126

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 MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD 210/SD 212/SD 205, SD 425, SD 430, SD 450, SD 617, SD 625, SD 650/52, SD 808, SD 810, SD 820, SD 835, SD 845, SD 850, and SDX20, possible buffer overflow when processing 1X circuit service message.

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

Buffer overflow vulnerability in Qualcomm Snapdragon modem firmware when processing 1X circuit service messages. The flaw exists in multiple Snapdragon mobile and Wear SoC variants (MDM9607, MDM9635M through SDX20) and allows potential remote code execution due to insufficient bounds checking on incoming circuit service data.

MitigationApply Android security patch level 2018-04-05 or later, or obtain OEM/firmware updates from Qualcomm addressing this modem buffer overflow vulnerability.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9645 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Sd 210 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 modem chip model
    Query the device's baseband/modem information using AT commands (e.g., 'AT+CGMM' or through Android diagnostic menus under Settings > About Phone > Baseband version) or check the SoC documentation for the specific chipset identifier
    Affected if The modem chip is one of: MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, or SD210
  2. Check the installed baseband firmware version
    Retrieve the baseband version via 'AT+CGMR' command, Android Settings > About Phone > Baseband, or through manufacturer diagnostic tools. Compare the version string against the affected product list
    Affected if The baseband firmware corresponds to any of the listed affected chipsets (all versions are affected)
  3. Determine if 1X circuit service is active or enabled
    Check if the device is connected to or capable of connecting to CDMA2000 1X networks. On Android, this can be seen in the mobile network settings or through diagnostic codes (e.g., *#*#4636#*#*). On feature phones, check network type indicators
    Affected if 1X circuit service is enabled and the device operates on or can connect to CDMA2000 1X networks, which is the attack vector for this vulnerability

The environment is affected if the device contains any of the listed Qualcomm modem chips (MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W, SD210) and has 1X circuit service enabled, as the buffer overflow is triggered during 1X circuit service message processing.

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 2018-04-05 or later, or obtain OEM/firmware updates from Qualcomm addressing this modem buffer overflow vulnerability.

Recommended fix Moderate confidence

Android devices with security patch level April 2018 or later

  1. Identify your device model and check with your device manufacturer for available Android security updates
  2. Update your Android device to the latest available system update that includes the April 2018 security patch level or later
  3. Verify the installed security patch level by going to Settings > About Phone > Security Patch Level and confirm it shows April 2018 or later
  4. If your device manufacturer no longer provides updates, consider upgrading to a newer device that receives regular security patches
  5. For embedded/IoT devices using the affected Qualcomm chipsets, contact the device manufacturer for firmware updates that address this vulnerability
Caveat Some older devices may not receive Android updates beyond a certain point due to hardware limitations or manufacturer support cycles

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

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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