dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2018-5915

CRITICAL · 9.8 CVSS v3.0 Published 2019-01-18
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
Exception in Modem IP stack while processing IPv6 packet in snapdragon automobile, snapdragon mobile and snapdragon wear in versions MDM9607, MDM9640, MDM9650, MSM8909W, MSM8996AU, SD 210/SD 212/SD 205, SD 425, SD 430, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SDA660, SDX20, 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

Exception (crash/unhandled error) in the modem IP stack when processing specifically crafted IPv6 packets. This is a baseband/modem firmware vulnerability affecting Qualcomm Snapdragon chipsets used in automotive, mobile, and wearable devices. The exception can likely cause modem crashes or potentially enable code execution given the critical severity.

MitigationApply vendor firmware updates from OEMs; this is a modem-level vulnerability requiring patches from Qualcomm distributed through device manufacturers. No user-level workarounds available.

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
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/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 Qualcomm chipset model
    Check the device specifications or use system information tools to determine if the device uses one of the affected chipsets: Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, Sd 210, Sd 212, or Sd 205. On Android, this may appear in /proc/cpuinfo or through apps like CPU-Z.
    Affected if The device does not contain one of the listed chipset models, then it is not affected.
  2. Retrieve the baseband firmware version
    Use AT command interface to query modem version. On Android, try 'AT+CGMR' or 'ATI' through a terminal app with modem diagnostics enabled, or check /proc/ baseband version files if accessible. Alternatively, check the device Settings > About Phone > Baseband version field.
    Affected if The baseband version cannot be determined or the device uses one of the listed chipsets with any firmware version, then it should be considered affected since all versions are vulnerable.
  3. Verify IPv6 connectivity is enabled
    Check if IPv6 is active on the device network interfaces. On Android, inspect network settings or use 'ip -6 addr' command to see if IPv6 addresses are assigned to cellular interfaces.
    Affected if IPv6 is enabled and the device contains an affected chipset, the vulnerability is exploitable in the attack vector described.
  4. Check for OEM firmware updates
    Contact the device manufacturer or check their support website for any available modem firmware updates that may address CVE-2018-5915.
    Affected if No vendor patch has been applied and the device uses an affected chipset, it remains vulnerable.

If the device contains any of the listed Qualcomm chipsets (Mdm9607, Mdm9640, Mdm9650, Msm8909w, Msm8996au, Sd 210, Sd 212, Sd 205) with any firmware version and has IPv6 enabled, the environment is affected by this baseband 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 firmware updates from OEMs; this is a modem-level vulnerability requiring patches from Qualcomm distributed through device manufacturers. No user-level workarounds available.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,740
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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