dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-11258

HIGH · 7.8 CVSS v3.0 Published 2018-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 ADSP RPC in Snapdragon Automobile, Snapdragon Mobile and Snapdragon Wear, a Use After Free condition can occur in versions MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 450, SD 615/16/SD 415, SD 625, SD 650/52, SD 820, SD 820A, SD 835, SD 845, SDX20.

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 Use After Free (UAF) vulnerability exists in ADSP RPC (Application Digital Signal Processor Remote Procedure Call) within multiple Qualcomm Snapdragon chipset variants. This memory corruption flaw allows an attacker to potentially execute arbitrary code or cause a denial of service by freeing memory and then accessing it after it has been deallocated.

MitigationApply vendor-supplied firmware updates from Qualcomm and downstream device OEMs. This vulnerability resides in DSP firmware, so remediation requires coordinated firmware updates across the affected device ecosystem.

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
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Sd 210 FirmwareOperating system
Affected:all versions
Sd 212 FirmwareOperating system
Affected:all versions
Sd 205 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/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 device chipset model
    Determine the Qualcomm chipset model used in your device or embedded system. This is typically found in device specifications, hardware documentation, or via system information commands (e.g., atrilist, lspci, or manufacturer APIs).
    Affected if The chipset matches one of the following: Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, Sd 210, Sd 212, or Sd 205
  2. Verify ADSP subsystem is present
    Check if the ADSP (Application Digital Signal Processor) subsystem is present and enabled on the device. On Android devices, this can be checked via /sys/class/remoteproc/ or through diagnostic logs. On embedded systems, check modem/processor subsystem status.
    Affected if The ADSP/DSP subsystem is present and operational on the device (which is the default state for affected chipsets)
  3. Confirm DSP RPC interface is active
    Inspect whether the ADSP RPC interface is exposed or accessible. This typically involves checking for running DSP-related services or RPC listeners. On Android, check services list or examine /vendor or /system partitions for DSP-related binaries.
    Affected if ADSP RPC services are running or the DSP subsystem is loaded at boot time (standard for these platforms)
  4. Check firmware version if accessible
    If you can access firmware version information (through manufacturer diagnostic tools, modem AT commands, or debug interfaces), retrieve the DSP/ADSP firmware version. Note: All versions of the listed chipsets are affected.
    Affected if The device uses any of the affected chipset models regardless of firmware version, as all versions are vulnerable

Your environment is affected if you deploy devices, IoT equipment, or embedded systems containing any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205) with the ADSP subsystem enabled, which is the default configuration.

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 vendor-supplied firmware updates from Qualcomm and downstream device OEMs. This vulnerability resides in DSP firmware, so remediation requires coordinated firmware updates across the affected device ecosystem.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation16.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA12.0 h
92.0 hours of engineering $16,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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