dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-5903

HIGH · 7.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 →
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
Out of bounds read occurs due to improper validation of array while processing VDEV stop response from WLAN firmware in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music in MDM9206, MDM9607, MDM9640, MDM9650, MSM8996AU, QCS405, QCS605, SD 210/SD 212/SD 205, SD 615/16/SD 415, SD 625, SD 636, SD 650/52, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820A, SD 835, SD 855, SDA660, SDM630, SDM660, SDX20, SDX24

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

Out-of-bounds read vulnerability in Qualcomm Snapdragon WLAN firmware. Improper validation of array bounds occurs when processing VDEV (Virtual Device) stop response messages from the WLAN firmware, allowing reading beyond allocated buffer boundaries.

MitigationApply vendor-supplied firmware/security patches from Qualcomm and device manufacturers. This is a firmware-level issue requiring updates to the WLAN firmware component.

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
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs405 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sd 210 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 the Qualcomm WLAN chip model
    Determine the specific Qualcomm chipset used in the device by checking hardware specifications, device schematics, or system information utilities that expose chip details. Look for model numbers such as Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8996au, Qcs405, Qcs605, or Sd 210.
    Affected if The device contains any of the following chips: Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8996au, Qcs405, Qcs605, or Sd 210
  2. Check the WLAN firmware version
    Access the device's firmware or system information interface to retrieve the installed WLAN firmware version. This may be available through debug logs, firmware dump utilities, or device management interfaces depending on the device type.
    Affected if The WLAN firmware version cannot be determined or is not listed as patched by Qualcomm security advisories
  3. Verify VDEV stop response handling is present
    Inspect the WLAN firmware binary or firmware configuration to confirm the presence of VDEV (Virtual Device) stop response message processing code. This component is part of the WLAN firmware stack.
    Affected if The VDEV stop response processing module exists in the installed firmware
  4. Confirm the vulnerability is unpatched
    Compare the installed firmware version against known vulnerable versions. Since all versions of the listed products are affected, check if a vendor security patch addressing CVE-2018-5903 has been applied.
    Affected if The device runs the affected chip with firmware that predates the CVE-2018-5903 patch or lacks any Qualcomm security update

A user is affected if their device uses any of the listed Qualcomm chipsets (Mdm9206, Mdm9607, Mdm9640, Mdm9650, Msm8996au, Qcs405, Qcs605, or Sd 210) and the WLAN firmware has not been updated with the vendor-supplied security patch.

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 manufacturers. This is a firmware-level issue requiring updates to the WLAN firmware component.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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