dbcve.org
Mdm9150 FirmwareOperating system · Qualcomm

CVE-2018-13898

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-14
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
Out-of-Bounds write due to incorrect array index check in PMIC in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in MDM9150, MDM9206, MDM9607, MDM9650, MDM9655, QCS405, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM439, SDM630, SDM660, SDX24, Snapdragon_High_Med_2016, SXR1130

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

An out-of-bounds write vulnerability exists in the Power Management IC (PMIC) firmware due to an incorrect array index check. This allows memory corruption by writing beyond array boundaries, potentially enabling arbitrary code execution or denial of service on affected Snapdragon-based devices.

MitigationApply firmware updates provided by device manufacturers that include the patched PMIC firmware from Qualcomm. Until patches are available, monitor device behavior for anomalous power management events.

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
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Qcs405 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qualcomm 215 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 PMIC hardware model
    Examine system logs, device tree files (/proc/device-tree/), or hardware diagnostic reports to determine the PMIC chip model. Look for identifiers such as Mdm9150, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Qcs405, Qcs605, or Qualcomm 215.
    Affected if The device contains any of the following PMIC models: Mdm9150, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Qcs405, Qcs605, or Qualcomm 215.
  2. Check PMIC firmware version
    Use manufacturer-specific diagnostic tools, debug interfaces (ADB, JTAG), or system information files to read the installed PMIC firmware version. Consult device manufacturer documentation for the exact command or file location.
    Affected if The PMIC firmware version matches any of the affected models listed (all versions are affected).
  3. Verify PMIC firmware is present and active
    Confirm that the device uses a Power Management IC by checking hardware initialization logs, boot messages, or PMIC-related system services. Verify the PMIC firmware is running on the device.
    Affected if The device actively uses PMIC firmware from the affected product list.

A device is affected if it contains any of the listed Qualcomm PMIC models (Mdm9150, Mdm9206, Mdm9607, Mdm9650, Mdm9655, Qcs405, Qcs605, or Qualcomm 215) and runs the corresponding firmware, as all versions of these products contain the vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates provided by device manufacturers that include the patched PMIC firmware from Qualcomm. Until patches are available, monitor device behavior for anomalous power management events.

Fix this in Mdm9150 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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