dbcve.org
Mdm9625 FirmwareOperating system · Qualcomm

CVE-2015-9147

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

In specific Qualcomm Snapdragon chips (MDM9625, MDM9635M, SD 400, SD 800) used in Android devices, userspace-provided pointer arguments are not validated before use. This input validation failure in the low-level driver/firmware code could allow an attacker to supply malicious pointer values, potentially leading to memory corruption, privilege escalation, or arbitrary code execution.

MitigationApply the Android security patch released April 2018 or later, which contains the fix for this pointer validation vulnerability. Organizations should inventory affected devices and prioritize patching given the critical CVSS score.

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 your device chip model
    Determine the exact model of your Android device and research its chipset specifications. Look for the baseband/modem processor (MDM series) or Snapdragon SoC (SD series) model number. This information is typically found in the device settings under 'About Phone' > 'Hardware' or 'Baseband', or by searching your device model specifications online.
    Affected if The device uses a Qualcomm MDM9625, MDM9635M, SD 400, or SD 800 chipset.
  2. Locate the baseband firmware version
    On Android, go to Settings > About Phone > Baseband version (or Modem version). Record the exact firmware version string displayed. This represents the low-level firmware running on the baseband/modem processor where the vulnerability exists.
    Affected if The baseband version corresponds to firmware that has not been updated since the April 2018 security patch.
  3. Check Android security patch level
    Go to Settings > About Phone > Android security patch level (or Settings > System > Security > Security patch level). Verify the date of the last security update installed.
    Affected if The security patch level is earlier than April 2018, indicating the fix for this pointer validation flaw has not been applied.
  4. Cross-reference chip and patch status
    Using the chip model identified and the patch level verified, determine if your specific device configuration matches the affected product list and whether the known patching timeline has been followed.
    Affected if The device contains an affected Qualcomm chip (MDM9625, MDM9635M, SD 400, or SD 800) AND the installed security patch predates the April 2018 release.

Your environment is affected if your Android device contains a Qualcomm MDM9625, MDM9635M, SD 400, or SD 800 chip and the Android security patch level is earlier than April 2018, meaning the firmware-level pointer validation fix has not been applied.

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 released April 2018 or later, which contains the fix for this pointer validation vulnerability. Organizations should inventory affected devices and prioritize patching given the critical CVSS score.

Recommended fix Moderate confidence

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

  1. 1. Navigate to Settings > About Phone on the affected Android device
  2. 2. Check the current Android security patch level under 'Security patch level'
  3. 3. If the security patch level is before 2018-04-05, the device is vulnerable
  4. 4. Go to Settings > System > Software Update (or Settings > About Phone > Software Update)
  5. 5. Check for updates and download/install any available security updates
  6. 6. Alternatively, contact the device manufacturer for the specific security patch update containing the fix for this vulnerability
  7. 7. Verify the security patch level is 2018-04-05 or later after updating

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
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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