dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-13909

HIGH · 7.0 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 →
72/100
Remediation priority · Elevated
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
Metadata verification and partial hash system calls by bootloader may corrupt parallel hashing state in progress resulting in unexpected behavior in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music in MDM9206, MDM9607, MDM9650, MDM9655, QCS605, Qualcomm 215, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 636, SD 712 / SD 710 / SD 670, SD 845 / SD 850, SD 8CX, SDA660, SDM439, SDM630, SDM660, 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 · moderate confidence

Vulnerability in Qualcomm Snapdragon bootloaders where metadata verification and partial hash system calls can corrupt parallel hashing state in progress, leading to unexpected behavior. The issue stems from race conditions or improper state management when multiple hash verification operations occur simultaneously during the boot process.

MitigationApply firmware updates provided by Qualcomm and device manufacturers. Users should ensure their devices are running the latest firmware版本 from their device OEM, as this is a low-level bootloader vulnerability that cannot be mitigated through software configuration changes.

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
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qm215 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 412 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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:L/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
    Check device specifications or use diagnostic tools (like CPU-Z, device info in settings, or ADB commands such as 'getprop ro.product.board' or 'cat /proc/cpuinfo') to identify the exact Qualcomm Snapdragon chipset
    Affected if The chipset matches one of the affected models: Mdm9206, Mdm9607, Mdm9650, Mdm9655, Qcs605, Qm215, Sd 410, or Sd 412
  2. Determine the firmware version
    Retrieve the bootloader or firmware version through device diagnostics, manufacturer tools, or ADB commands such as 'getprop ro.build.id' or 'getprop ro.bootloader'
    Affected if The firmware version corresponds to the listed affected products (all versions of the listed firmware are vulnerable)
  3. Check if secure boot with hash verification is enabled
    Inspect bootloader configuration settings. On supported devices, this may be accessible through fastboot mode ('fastboot oem device-info') or manufacturer-specific diagnostic interfaces. The vulnerability exists when metadata verification or hash system calls are performed during boot
    Affected if Secure boot or metadata verification features are enabled on the bootloader, as the flaw manifests during hash verification operations

Your device is affected if it uses one of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9650, Mdm9655, Qcs605, Qm215, Sd 410, or Sd 412) with any firmware version and has bootloader-based hash verification enabled.

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 Qualcomm and device manufacturers. Users should ensure their devices are running the latest firmware版本 from their device OEM, as this is a low-level bootloader vulnerability that cannot be mitigated through software configuration changes.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,960
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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