dbcve.org
Mdm9150 FirmwareOperating system · Qualcomm

CVE-2018-13918

HIGH · 7.8 CVSS v3.0 Published 2019-04-04
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
kernel could return a received message length higher than expected, which leads to buffer overflow in a subsequent operation and stops normal operation in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables, in MDM9150, MDM9206, MDM9607, MDM9650, MSM8909W, QCS605, Qualcomm 215, SD 425, SD 439 / SD 429, SD 450, SD 625, SD 632, SD 675, SD 712 / SD 710 / SD 670, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDM439, SDX24, SM7150

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

The kernel returns a received message length higher than expected, which causes a buffer overflow in a subsequent operation. This kernel-level flaw allows the returned length to exceed buffer boundaries, leading to potential denial of service or undefined behavior.

MitigationApply vendor-supplied firmware updates for affected Snapdragon processors that include the kernel patch to properly validate returned message lengths before use in subsequent operations.

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
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qm215 FirmwareOperating system
Affected:all versions
Sd 425 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 chipset model in the device
    Check system information or hardware specifications to determine the exact Qualcomm Snapdragon model number (e.g., Mdm9150, Mdm9206, Mdm9607, Mdm9650, Msm8909w, Qcs605, Qm215, or Sd 425). This may be found in /proc/cpuinfo, device settings, or hardware documentation.
    Affected if The chipset model matches any of the following: Mdm9150, Mdm9206, Mdm9607, Mdm9650, Msm8909w, Qcs605, Qm215, or Sd 425.
  2. Determine the installed firmware version
    Retrieve the firmware version string from the device. On Linux-based systems, this may be available via 'cat /sys/firmware/devicetree/base/model', 'dmesg', 'cat /proc/version', or vendor-specific diagnostic tools. Check the device settings or boot logs for version information.
    Affected if The firmware version cannot be determined or is older than vendor-patched versions.
  3. Verify kernel message handling configuration
    Examine kernel configuration or runtime settings related to network message handling if accessible. Look for any non-default network protocol handlers or message parsing modules that process external input.
    Affected if Non-standard or custom network message handling modules are enabled that could trigger the vulnerable code path.
  4. Check for vendor security advisories
    Search for the specific CVE identifier (CVE-2018-13918) in vendor security advisories or firmware release notes to confirm if a patch has been applied to your specific firmware version.
    Affected if No vendor security patch for CVE-2018-13918 has been applied to the installed firmware version.

The device is affected if it uses any of the listed Qualcomm chipsets (Mdm9150, Mdm9206, Mdm9607, Mdm9650, Msm8909w, Qcs605, Qm215, or Sd 425) and the firmware has not been updated to include the vendor patch for this kernel buffer overflow vulnerability.

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 for affected Snapdragon processors that include the kernel patch to properly validate returned message lengths before use in subsequent operations.

Fix this in Mdm9150 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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