dbcve.org
Mdm9625 FirmwareOperating system · Qualcomm

CVE-2015-9150

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 MDM9625, MDM9635M, SD 400, and SD 800, while computing the length of memory allocated for a Diag event, if the buffer length is very small or greater than the maximum, an integer overflow may occur, which later results in a buffer overflow.

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 · moderate confidence

Integer overflow vulnerability in Qualcomm Snapdragon Diag event memory allocation on MDM9625, MDM9635M, SD 400, and SD 800 chips. When computing allocation length with a buffer length that is very small or exceeds maximum, an integer overflow occurs, leading to subsequent buffer overflow.

MitigationApply Android security patch level from 2018-04-05 or later, or obtain and deploy vendor-specific firmware updates for affected Snapdragon devices.

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
Mdm9625 FirmwareOperating system
Affected:all versions
Mdm9635m FirmwareOperating system
Affected:all versions
Sd 400 FirmwareOperating system
Affected:all versions
Sd 800 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 chip model
    Check /proc/cpuinfo or use 'cat /sys/devices/system/cpu/cpu0/cpu_variant' or check boot logs for chip identifiers like MDM9625, MDM9635M, SD400, or SD800
    Affected if The chip model is one of: MDM9625, MDM9635M, SD400, or SD800
  2. Verify Diag diagnostic interface is active
    Check if /dev/diag or /dev/diag_arm9 exists and is accessible, or check if 'diag' kernel module is loaded via 'lsmod | grep diag' or 'getprop persist.service.diag' on Android
    Affected if The Diag device interface is present and accessible (vulnerability requires Diag to be enabled)
  3. Check firmware/baseband version
    Check /proc/version, /proc/cmdline, or use 'getprop' commands (getprop ro.build.version.release, getprop ro.baseband) to identify the firmware version
    Affected if Firmware matches the affected product line (MDM9625, MDM9635M, SD400, SD800) and all versions are affected according to the advisory

You are affected if your device uses a Qualcomm MDM9625, MDM9635M, SD400, or SD800 chip AND the Diag diagnostic interface is enabled on the system.

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 2018-04-05 or later, or obtain and deploy vendor-specific firmware updates for affected Snapdragon devices.

Recommended fix High confidence

Android Security Patch Level 2018-04-05 or later (delivered via OEM firmware update)

  1. Identify the affected device model and ensure it supports Android security updates
  2. Check the current Android Security Patch Level on the device (Settings > About Phone > Android security patch level)
  3. If the device is on Android with Security Patch Level before 2018-04-05, apply the available system update from the device manufacturer
  4. Verify the device now shows Security Patch Level of 2018-04-05 or later
  5. For embedded/mobile devices using these specific modem components (MDM9625, MDM9635M, SD 400, SD 800), contact the device OEM for firmware updates that include the Qualcomm modem fix
Caveat Device must be supported by OEM for security updates; older devices may not receive patches

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

Fix this in Mdm9625 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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