dbcve.org
Mdm9625 FirmwareOperating system · Qualcomm

CVE-2015-9151

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, userspace-provided pointer arguments are not validated.

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

This vulnerability exists in the Qualcomm Snapdragon baseband/processor firmware for specific MDM9635M, MDM9625, SD 400, and SD 800 chips. The kernel or driver code fails to validate pointers passed from userspace, allowing an attacker to potentially manipulate memory addresses and achieve privilege escalation or arbitrary code execution. This is a classic input validation flaw in low-level system code.

MitigationApply the Android security patch level from 2018-04-05 or later, which contains the fix for this vulnerability. Organizations should identify affected devices in their fleet and prioritize patching or replacement, as these older chipsets may have limited or no further security support.

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 chipset model
    Check the device specifications or use commands like 'lspci', 'lsusb', or check /proc/cpuinfo to determine if the device uses a Qualcomm MDM9635M, MDM9625, SD 400, or SD 800 chip
    Affected if The device uses any of these four chipset models (MDM9635M, MDM9625, SD 400, SD 800)
  2. Check baseband firmware version
    On Android devices, go to Settings > About Phone > Baseband version or use 'AT+CGMR' command in terminal emulator to retrieve the baseband firmware version
    Affected if The baseband firmware version is present and matches one of the affected chips (indicating all versions are potentially vulnerable)
  3. Check processor/system-on-chip info
    Check /proc/cpuinfo, use 'lshw', or view device specs to confirm the Snapdragon processor model
    Affected if The processor is identified as SD 400 or SD 800 from the Snapdragon 400 or 800 series
  4. Verify Android security patch level
    Go to Settings > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' in ADB/shell
    Affected if The security patch level is earlier than 2018-04-05 or is not listed (indicating the fix has not been applied)

The device is affected if it contains a Qualcomm MDM9635M, MDM9625, SD 400, or SD 800 chip and has an Android security patch level earlier than April 5, 2018.

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 Android security patch level from 2018-04-05 or later, which contains the fix for this vulnerability. Organizations should identify affected devices in their fleet and prioritize patching or replacement, as these older chipsets may have limited or no further security support.

Recommended fix Moderate confidence

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

  1. Ensure your device receives the Android Security Patch Level 2018-04-05 or later
  2. Contact your device OEM (Original Equipment Manufacturer) to verify firmware update availability for your specific device model
  3. If your device OEM no longer supports updates, consider migrating to a newer device that receives active security patches
  4. For enterprise environments, apply the OEM-provided firmware update through your mobile device management (MDM) system once available
Caveat Older devices (MDM9625, MDM9635M, SD 400, SD 800) may no longer receive security updates from OEMs; end-of-life devices may require replacement

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

Fix this in Mdm9625 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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