dbcve.org
Apq8017 FirmwareOperating system · Qualcomm

CVE-2019-10592

HIGH · 7.8 CVSS v3.1 Published 2019-12-12
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
Possible integer overflow while multiplying two integers of 32 bit in QDCM API of get display modes as there is no check on the maximum mode count in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8017, APQ8053, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MSM8909, MSM8909W, MSM8917, MSM8920, MSM8937, MSM8940, MSM8953, MSM8996AU, MSM8998, Nicobar, QCS405, QCS605, QM215, SDA660, SDA845, SDM429, SDM439, SDM450, SDM630, SDM632, SDM636, SDM660, SDM670, SDM710, SDM845, SDX20, SM6150, SM7150, SM8150, SM8250, SXR1130, 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

Integer overflow vulnerability in Qualcomm QDCM (Display Color Management) API when multiplying two 32-bit integers to calculate display mode count. The lack of bounds checking on the mode count multiplication allows an attacker to trigger heap overflow conditions, potentially leading to arbitrary code execution in the display subsystem.

MitigationApply vendor-supplied firmware/security patch updates from OEM/device manufacturers. This is a chipset-level vulnerability requiring firmware updates from Qualcomm and subsequent OEM deployment.

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
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Apq8098 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Msm8909 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.1/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
    Determine the exact chipset (Apq8017, Apq8053, Apq8096au, Apq8098, Mdm9206, Mdm9207c, Mdm9607, or Msm8909) used in the device. This can be done via /proc/cpuinfo on Android devices, or through system information utilities.
    Affected if The chipset matches one of the eight affected models listed in the CVE.
  2. Check the firmware version
    Retrieve the firmware version from the device. On Android, this may be available through_settings > About Phone, via AT commands, or through /proc/version. Compare against vendor release notes if version information is available.
    Affected if The device runs on any firmware version of the affected chipsets, as the CVE states all versions are affected.
  3. Verify QDCM API availability
    Check if the Qualcomm Display Color Management (QDCM) functionality is present and enabled on the system. This may involve inspecting system logs, looking for qdcm or display color management related services, or checking /vendor or /system/etc for related libraries.
    Affected if QDCM API is present and actively used by the display subsystem.
  4. Inspect display driver configuration
    Examine the display driver or display configuration files for the mode count calculation logic. Look for code that performs multiplication of two 32-bit integers related to display modes without proper bounds checking.
    Affected if The display configuration contains code paths that perform unchecked multiplication of display mode parameters.

A device is affected if it uses any of the eight listed Qualcomm chipsets (Apq8017, Apq8053, Apq8096au, Apq8098, Mdm9206, Mdm9207c, Mdm9607, Msm8909) and utilizes the QDCM display color management functionality.

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 patch updates from OEM/device manufacturers. This is a chipset-level vulnerability requiring firmware updates from Qualcomm and subsequent OEM deployment.

Fix this in Apq8017 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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