dbcve.org
Mdm9650 FirmwareOperating system · Qualcomm

CVE-2018-11932

CRITICAL · 9.1 CVSS v3.0 Published 2019-02-25
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
Improper input validation can lead RW access to secure subsystem from HLOS in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in versions MDM9650, MDM9655, MSM8996AU, QCS605, SD 410/12, SD 615/16/SD 415, SD 675, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 8CX, 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

This vulnerability in Qualcomm Snapdragon chipsets allows improper input validation that enables read/write access from the High-Level Operating System (HLOS) to the secure subsystem, breaking the security boundary meant to isolate trusted execution environments from the main OS.

MitigationApply vendor-supplied firmware/security patches from Qualcomm and device OEMs. Users should apply available security updates for affected devices.

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
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sd 410 FirmwareOperating system
Affected:all versions
Sd 12 FirmwareOperating system
Affected:all versions
Sd 615 FirmwareOperating system
Affected:all versions
Sd 16 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
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 the processor information on the device. On Android, this can be found in Settings > About Phone > Processor, or by examining /proc/cpuinfo for the hardware identifier. On Linux systems, use 'cat /proc/cpuinfo' or 'lscpu' to identify the chipset.
    Affected if The chipset matches one of the affected models: Mdm9650, Mdm9655, Msm8996au, Qcs605, Sd 410, Sd 12, Sd 615, or Sd 16.
  2. Check the baseband or firmware version
    On Android devices, go to Settings > About Phone > Baseband version or Settings > About Phone > Kernel version. The exact location varies by device. Alternatively, use 'getprop' commands such as 'getprop ro.baseband' or 'getprop gsm.version.baseband' to retrieve firmware version information.
    Affected if The device firmware version has not been patched. Since all versions of the affected firmware are vulnerable, compare against the latest vendor-supplied security patch level.
  3. Verify the Android security patch level
    On Android, go to Settings > About Phone > Android security patch level. This shows when the last security update was applied. The patch for this CVE was included in the Qualcomm security bulletin from April 2018.
    Affected if The security patch level is earlier than April 2018, or if no security patches have been applied to the device.
  4. Check if secure subsystem access is properly restricted
    Review whether applications or processes from the HLOS can access the secure subsystem or TEE (Trusted Execution Environment). This typically requires examining system logs, security configurations, or using tools like 'dmesg' to look for access attempts. On Android, check SELinux policies that govern secure subsystem access.
    Affected if The HLOS can read from or write to the secure subsystem without proper authentication or restrictions, indicating the vulnerability is present and exploitable.

A user is affected if their device contains one of the listed Qualcomm chipsets and the vendor security patches from April 2018 or later have 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.

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

Apply vendor-supplied firmware/security patches from Qualcomm and device OEMs. Users should apply available security updates for affected devices.

Fix this in Mdm9650 Firmware Scoped from the published advisory
  • Consultation8.0 h
8.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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