dbcve.org
Mdm9607 FirmwareOperating system · Qualcomm

CVE-2019-14075

MEDIUM · 5.5 CVSS v3.1 Published 2020-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Null pointer dereference issue in radio interface layer due to lack of null check in sapmodule destructor in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in MDM9607, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8998, Nicobar, QCS605, Rennell, Saipan, SDM450, SDM630, SDM636, SDM660, SDM670, SDM710, SM6150, SM7150, SM8150, SM8250, SXR2130

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 null pointer dereference vulnerability exists in the radio interface layer (RIL) of Qualcomm Snapdragon chipsets. The issue is in the sapmodule destructor, which lacks proper null checking before dereferencing a pointer. This causes a kernel or system crash when the destructor executes with a null pointer, leading to denial of service. The vulnerability affects 23 different Snapdragon chipset variants across mobile, automotive, consumer IoT, and industrial IoT platforms.

MitigationApply vendor-supplied firmware/security updates from the device OEM that include the patched radio interface layer. Since this is a baseband/radio firmware issue, users must obtain updates from their device manufacturer rather than through traditional OS patches.

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
Msm8917 FirmwareOperating system
Affected:all versions
Msm8920 FirmwareOperating system
Affected:all versions
Msm8937 FirmwareOperating system
Affected:all versions
Msm8940 FirmwareOperating system
Affected:all versions
Msm8953 FirmwareOperating system
Affected:all versions
Msm8998 FirmwareOperating system
Affected:all versions
Nicobar 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 chipset model
    Check the device or system's processor/chipset information. On Android, this may be found in /proc/cpuinfo or through settings. For other systems, check BIOS/UEFI or system information utilities. Look for model numbers: Mdm9607, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, Msm8998, or Nicobar.
    Affected if The chipset matches any of the listed affected models (Mdm9607, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, Msm8998, or Nicobar)
  2. Verify the chipset is a Qualcomm Snapdragon
    Confirm the identified chipset belongs to the Qualcomm Snapdragon product line. These are ARM-based processors commonly found in mobile devices, automotive systems, IoT devices, and industrial equipment.
    Affected if The chipset is confirmed to be a Qualcomm Snapdragon variant matching the affected models
  3. Check baseband/radio firmware version
    Access the baseband or radio firmware version information. On Android devices, this is typically found in Settings > About Phone > Baseband version, or via AT commands (such as AT+CGMR or ATI) through a terminal emulator. For embedded systems, consult manufacturer documentation for firmware version retrieval.
    Affected if The baseband firmware version can be retrieved (all versions of the listed chipsets are affected per the advisory)
  4. Identify RIL and sapmodule usage
    Check if the Radio Interface Layer (RIL) and SAP (Serial Audio Protocol) module are active on the system. On Android, examine /system/lib/libreference-ril.so or similar RIL libraries. Review system logs (logcat) for sapmodule or RIL-related processes and functionality.
    Affected if The system utilizes a RIL implementation with sapmodule functionality, as the vulnerability exists in the sapmodule destructor

If the device uses any of the affected Qualcomm Snapdragon chipset models (Mdm9607, Msm8917, Msm8920, Msm8937, Msm8940, Msm8953, Msm8998, or Nicobar) and utilizes the Radio Interface Layer with sapmodule, the environment is considered affected since all firmware versions of these chipsets contain the 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/security updates from the device OEM that include the patched radio interface layer. Since this is a baseband/radio firmware issue, users must obtain updates from their device manufacturer rather than through traditional OS patches.

Fix this in Mdm9607 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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