dbcve.org
Mdm9206 FirmwareOperating system · Qualcomm

CVE-2018-13925

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-24
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
Error in parsing PMT table frees the memory allocated for the map section but does not reset the context map section reference causing heap use after free issue in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Wearables in MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 600, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 712 / SD 710 / SD 670, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 855, SDA660, SDM439, SDM630, SDM660, SDX20, Snapdragon_High_Med_2016, 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

Heap use-after-free vulnerability in PMT (Program Map Table) parsing. The parser frees memory allocated for the map section but fails to reset the context map section reference, leading to dangling pointers that can be reused after free. This allows potential remote code execution or denial of service.

MitigationApply vendor-supplied firmware updates from Qualcomm and device manufacturers. Until patches are available, limit exposure by avoiding untrusted input streams and network connections to 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
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Qm215 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
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 baseband/modem firmware version
    Query the modem via AT command 'AT+CGMR' or check /proc/version, /sys/kernel/debug/smd/control, or use qdmx/diag interfaces depending on device access level
    Affected if The firmware version matches one of the affected Qualcomm variants (Mdm9206, Mdm9607, Mdm9650, Msm8909w, Msm8996au, Qcs605, Qm215, Sd 210) and has not been patched past the CVE disclosure date
  2. Determine if PMT parsing is active
    Monitor network traffic or examine if the device is processing MPEG Transport Streams (MPEG-TS), Digital TV broadcasts, or IP-based media streams that contain PMT sections
    Affected if The device is actively parsing or processing MPEG-TS/PMT data from untrusted sources such as over-the-air broadcasts, streaming inputs, or network sources
  3. Verify the device configuration for media input processing
    Check device settings, driver configuration, or media pipeline logs for active PMT/PCR parsing modules. On Android, examine /d/dri/0 or media server logs for PMT handler activity
    Affected if PMT parsing is enabled and the device processes broadcast or streaming media content containing Program Map Tables
  4. Check for crash logs or memory corruption indicators
    Review /proc/kmsg, dmesg, modem logs, or crash dump files for use-after-free errors related to PMT parsing, memory corruption, or unexpected NULL pointer dereferences in the media/transport module
    Affected if Any crash logs show memory corruption or dangling pointer behavior in PMT parsing code paths

The device is affected if it runs any unpatched Qualcomm firmware variant listed and processes MPEG-TS/PMT content from any input source, enabling the vulnerable parsing code path to be triggered.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates from Qualcomm and device manufacturers. Until patches are available, limit exposure by avoiding untrusted input streams and network connections to affected devices.

Recommended fix Moderate confidence
  1. Contact the device OEM (Original Equipment Manufacturer) that uses the affected Qualcomm chipset (MDM9206, MDM9607, MDM9650, MSM8909W, MSM8996AU, QCS605, QM215, SD 210) to obtain a firmware/security update
  2. Verify the device is running the latest available firmware version from the OEM
  3. If no patch is available from the OEM, monitor Qualcomm's product security bulletins for the availability of a fix
  4. Apply the OEM-provided security update once available
Caveat Firmware updates may introduce compatibility issues with carrier networks or device functionality; test thoroughly before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mdm9206 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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