dbcve.org
Apq8053 FirmwareOperating system · Qualcomm

CVE-2019-14047

HIGH · 7.8 CVSS v3.1 Published 2020-06-22
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
While IPA driver processes route add rule IOCTL, there is no input validation of the rule ID prior to adding the rule to the IPA HW commit list in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8053, APQ8096AU, MDM9607, MSM8909W, MSM8996, MSM8996AU, QCN7605, QCS605, SC8180X, SDA845, SDX20, SDX24, SDX55, 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 · high confidence

A missing input validation vulnerability exists in the Qualcomm IPA (Internet Protocol Accelerator) driver where the rule ID is not validated before being added to the IPA hardware commit list during route add rule IOCTL processing. This could allow an attacker to trigger memory corruption by providing an invalid or malicious rule ID, potentially leading to denial of service or code execution in the kernel context.

MitigationApply vendor-supplied firmware/driver updates that implement proper input validation for rule IDs in the IPA driver's IOCTL handler. This is a kernel-level fix requiring updates from Qualcomm or device OEMs.

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
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Msm8909w FirmwareOperating system
Affected:all versions
Msm8996 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qcn7605 FirmwareOperating system
Affected:all versions
Qcs605 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 SoC model in the device
    Check the system-on-chip or baseband processor by reviewing /proc/cpuinfo, kernel boot logs, or device hardware specifications. Look for identifiers such as Apq8053, Apq8096au, Mdm9607, Msm8909w, Msm8996, Msm8996au, Qcn7605, or Qcs605.
    Affected if The device uses any of the listed Qualcomm chip models (Apq8053, Apq8096au, Mdm9607, Msm8909w, Msm8996, Msm8996au, Qcn7605, Qcs605)
  2. Determine the firmware version of the Qualcomm component
    Check the baseband or radio firmware version via AT commands (for modems), through /proc/version, /sys/firmware, or OEM-specific diagnostic interfaces. Compare the firmware version against the affected product list.
    Affected if The firmware version corresponds to any of the listed products (all versions are affected)
  3. Verify if the IPA driver is loaded
    Check for the presence of the IPA driver module in the kernel. Look for 'ipa' in /proc/modules, or check for 'ipa' in lsmod output, or inspect /sys/kernel/debug/ipa/ if debugfs is available.
    Affected if The IPA (Internet Protocol Accelerator) driver is present and loaded in the kernel
  4. Check for access to the IPA route add rule IOCTL interface
    Inspect /dev/ipa or similar device nodes used for IPA driver communication. Look for IOCTL calls related to route add rule functionality by examining driver source code or using tools like strace on processes that interact with IPA.
    Affected if The IOCTL interface for route add rule (IPA_IOC_ADD_RULE) is exposed and accessible to user space or untrusted components

The device is affected if it uses any of the listed Qualcomm SoC models with IPA driver support, since all firmware versions for these products contain the unvalidated rule ID vulnerability in the IPA driver's IOCTL handler.

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/driver updates that implement proper input validation for rule IDs in the IPA driver's IOCTL handler. This is a kernel-level fix requiring updates from Qualcomm or device OEMs.

Fix this in Apq8053 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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