dbcve.org
Mdm9150 FirmwareOperating system · Qualcomm

CVE-2019-2239

MEDIUM · 5.5 CVSS v3.0 Published 2019-07-25
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
Sanity checks are missing in layout which can lead to SUI Corruption or can lead to Denial of Service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in MDM9150, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9650, MDM9655, MSM8996AU, QCS404, QCS605, Qualcomm 215, SD 210/SD 212/SD 205, SD 410/12, SD 425, SD 427, SD 430, SD 435, SD 439 / SD 429, SD 450, SD 615/16/SD 415, SD 625, SD 632, SD 636, SD 650/52, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 820A, SD 835, SD 845 / SD 850, SD 8CX, SDA660, SDM439, SDM630, SDM660, SDX20, SDX24, 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 · moderate confidence

Missing sanity checks in the layout processing component of Qualcomm Snapdragon chips can allow an attacker to cause System UI corruption or trigger a denial of service condition. The vulnerability exists in the layout handling code where improper validation of input data or parameters can lead to memory corruption or system instability.

MitigationApply the vendor-supplied firmware/driver update from Qualcomm. This is a platform-level fix requiring OEM firmware updates for affected devices. Users should monitor for and apply security patches from their device manufacturers.

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
Mdm9635m FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 FirmwareOperating system
Affected:all versions
Mdm9655 FirmwareOperating system
Affected:all versions
Msm8996au 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.0/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 /proc/cpuinfo or /sys/devices/system/cpu/ for Qualcomm chip identifiers such as Mdm9150, Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9650, Mdm9655, or Msm8996au
    Affected if The device uses any of the listed chipset models (Mdm9150, Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9650, Mdm9655, or Msm8996au)
  2. Check firmware version
    Query the baseband or radio firmware version via AT command (AT+CGMR) or through /proc/version, /proc/cpuinfo, or manufacturer-specific diagnostic tools
    Affected if The firmware version corresponds to any version of the affected chipsets listed - all versions of these products are vulnerable
  3. Verify layout processing component is active
    Monitor for System UI (com.android.systemui) crashes or anomalies in logcat (adb logcat) or bug reports, which indicate the layout processing component is being exercised
    Affected if System UI crashes or rendering anomalies occur, suggesting the layout handling code path is active and potentially exploitable
  4. Check for security patch level
    Check the Android security patch level via settings (Settings > About Phone > Security Patch Level) or via 'getprop ro.build.version.security_patch' command
    Affected if The security patch level is earlier than the date when this CVE was addressed (typically the October 2019 Android Security Patch or later)

The device is affected if it uses any of the listed Qualcomm chipset models (Mdm9150, Mdm9206, Mdm9607, Mdm9635m, Mdm9640, Mdm9650, Mdm9655, or Msm8996au) and has not received vendor firmware updates addressing this 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 the vendor-supplied firmware/driver update from Qualcomm. This is a platform-level fix requiring OEM firmware updates for affected devices. Users should monitor for and apply security patches from their device manufacturers.

Fix this in Mdm9150 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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