dbcve.org
Qcn7605 FirmwareOperating system · Qualcomm

CVE-2019-14085

HIGH · 7.8 CVSS v3.1 Published 2020-03-05
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 underflow in WLAN function due to lack of check of data received from user side in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile in QCN7605, QCS605, SDA845, SDM670, SDM710, SDM845, SDM850, SM8150, 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

Integer underflow vulnerability in WLAN function of Qualcomm Snapdragon chipsets caused by insufficient validation of user-supplied data before arithmetic operations, potentially allowing local privilege escalation or denial of service.

MitigationApply vendor-supplied firmware/security patches for affected Snapdragon chipsets; implement proper input validation and bounds checking in WLAN driver code to prevent underflow conditions.

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
Qcn7605 FirmwareOperating system
Affected:all versions
Qcs605 FirmwareOperating system
Affected:all versions
Sda845 FirmwareOperating system
Affected:all versions
Sdm670 FirmwareOperating system
Affected:all versions
Sdm710 FirmwareOperating system
Affected:all versions
Sdm845 FirmwareOperating system
Affected:all versions
Sdm850 FirmwareOperating system
Affected:all versions
Sm8150 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 in the device
    Check device system information, dmesg logs, or /proc/cpuinfo for chipset identification. On mobile devices, check Settings > About Phone > Model or use 'getprop ro.board.platform' or 'cat /sys/devices/soc0/family'
    Affected if The chipset matches one of the affected models: Qcn7605, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, Sdm850, or Sm8150
  2. Verify WLAN functionality is present and enabled
    Check if the WLAN driver module is loaded: 'lsmod | grep wlan' or check for wlan0 interface via 'ip link show'. On Android, use 'getprop wlan.driver.status' or check /sys/class/net/wlan0
    Affected if WLAN interface exists or WLAN driver is loaded, indicating the vulnerable WLAN function is active
  3. Check the WLAN firmware version
    Retrieve firmware version from /sys/class/net/wlan0/firmware_revision, /sys/kernel/debug/wlan/fw_version, or check wlan driver logs via 'dmesg | grep -i wlan'. On Android, check 'getprop ro.wlan.driver'
    Affected if Any firmware version is reported, confirming the WLAN component is operational (all versions of affected chipsets are vulnerable)
  4. Confirm firmware patch level
    Check security patch date in Settings > Security > Security patch level on Android, or 'getprop ro.build.version.security_patch'. Also check 'cat /proc/version' for kernel version which may reference firmware dates
    Affected if Security patch level is earlier than the vendor release date for this CVE fix (typically early 2020 releases for this vulnerability)

A device using any of the affected Qualcomm Snapdragon chipset models (Qcn7605, Qcs605, Sda845, Sdm670, Sdm710, Sdm845, Sdm850, Sm8150) with WLAN functionality enabled and an unpatched firmware version is vulnerable to this integer underflow flaw.

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 patches for affected Snapdragon chipsets; implement proper input validation and bounds checking in WLAN driver code to prevent underflow conditions.

Fix this in Qcn7605 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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