dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-11982

HIGH · 8.8 CVSS v3.0 Published 2018-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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 Snapdragon (Mobile, Wear) in version MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MDM9655, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 450, SD 615/16/SD 415, SD 617, SD 625, SD 650/52, SD 810, SD 820, SD 835, Snapdragon_High_Med_2016, a double free of ASN1 heap memory used for EUTRA CAP container occurs during UTRAN to LTE Capability inquiry procedure.

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 double-free vulnerability in the ASN1 heap memory handler for EUTRA CAP container within Qualcomm Snapdragon baseband firmware. The flaw occurs during UTRAN to LTE Capability inquiry procedure, allowing heap memory corruption that could enable remote code execution or denial of service.

MitigationApply Qualcomm-provided firmware security updates to affected Snapdragon chipsets; device OEMs must integrate and distribute the patch through their update mechanisms.

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
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/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 baseband chipset model
    Query the device or baseband processor information via AT commands (e.g., AT+CGMM) or through system information fields (such as /proc/bootinfo or Android's radio version properties). Confirm it is one of: Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9655, Msm8909w, or Msm8996au.
    Affected if The device uses any of the listed Qualcomm Snapdragon baseband chipsets.
  2. Check the baseband firmware version
    Retrieve the baseband firmware version using AT commands (e.g., AT+CGMR) or through system properties (e.g., 'getprop gsm.version.baseband'). Compare against the affected list - all versions of the listed chipsets are affected.
    Affected if The baseband firmware version corresponds to any of the listed Qualcomm chipsets, as all versions are affected.
  3. Verify LTE capability handling is enabled
    Confirm the device supports LTE (4G) networks by checking network capability settings or modem configuration. The vulnerability exists in the EUTRA CAP (LTE Capability) container parser, so LTE must be active for the flaw to be reachable.
    Affected if LTE capability is enabled and the device operates on or transitions to LTE networks.
  4. Monitor for ASN1 heap corruption indicators
    Review baseband crash logs, modem debug logs, or device kernel logs (via dmesg, logcat, or vendor-specific logs) for signs of heap corruption, double-free errors, or crashes originating from the ASN1 parsing module during network capability exchanges.
    Affected if Heap corruption or double-free errors appear in logs during UTRAN to LTE capability inquiry procedures.

A device is affected if it uses any of the listed Qualcomm Snapdragon baseband chipsets (Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9645, Mdm9655, Msm8909w, Msm8996au) and supports LTE capability, as all firmware versions of these chipsets contain the vulnerable ASN1 heap memory handler.

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 Qualcomm-provided firmware security updates to affected Snapdragon chipsets; device OEMs must integrate and distribute the patch through their update mechanisms.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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