dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2015-9145

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 Automobile, Snapdragon Mobile, and Snapdragon Wear MDM9206, 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 820A, SD 835, SD 845, SD 850, and SDX20, lack of input validation in NPA driver functions leads to null pointer dereference.

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 null pointer dereference vulnerability in the Qualcomm NPA (Native Portability Abstraction) driver due to lack of input validation. This driver-level flaw affects multiple Snapdragon chipset variants used in mobile, automotive, and wearable devices, potentially allowing denial of service or code execution.

MitigationApply Android security updates released on or after April 5, 2018, which contain the patch for this vulnerability. Users of affected devices should check with their device OEMs for available updates.

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
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

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
    Use device information utilities (such as 'lspci' for PCIe devices, 'cat /proc/cpuinfo', or manufacturer diagnostic tools) to determine the exact Qualcomm chipset variant (e.g., Mdm9206, Mdm9607, Msm8909w)
    Affected if The chipset model matches any of the following: Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w
  2. Determine the firmware version
    Query the device firmware version through manufacturer-specific diagnostic interfaces, bootloader information, or system firmware dump utilities (e.g., 'cat /sys/firmware/fw_version' or vendor-provided tools)
    Affected if The installed firmware version is any version of the affected chipset models listed above (the vulnerability affects all versions)
  3. Verify the NPA driver is present
    Check for the presence of the Native Portability Abstraction (NPA) driver module in the kernel or firmware (e.g., 'lsmod' or inspect /proc/modules, or check /sys/kernel/debug drivers)
    Affected if The NPA driver is loaded or compiled into the kernel - the vulnerability exists in this driver due to missing input validation

A device is affected if it uses any of the listed Qualcomm chipset models (Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9650, Mdm9655, or Msm8909w) with any firmware version and has the NPA driver present.

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 updates released on or after April 5, 2018, which contain the patch for this vulnerability. Users of affected devices should check with their device OEMs for available updates.

Recommended fix Moderate confidence

Android Security Patch Level 2018-04-05 or later (contact device manufacturer for specific modem firmware updates for MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9650, MDM9655, MSM8909W)

  1. Verify the current Android security patch level on the device (Settings > About Phone > Security Patch Level)
  2. Update the device to an Android security patch level released on or after April 5, 2018
  3. If the device manufacturer has released a modem firmware update, apply that update through the manufacturer's recommended process
  4. After updating, verify the security patch level reflects April 2018 or later
Caveat Some older devices may not receive Android security updates beyond a certain date; contact device manufacturer for support eligibility

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

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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