dbcve.org
Apq8053 FirmwareOperating system · Qualcomm

CVE-2019-10603

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
Use after free issue occurs If the real device interface goes down and a route lookup is performed while sending a raw IPv6 message in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables in APQ8053, APQ8096AU, APQ8098, MDM9206, MDM9207C, MDM9607, MDM9640, MDM9650, MSM8917, MSM8937, MSM8996AU, QCN7605, SDA845, SDM630, SDM636, SDM660, SDX20, 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 use-after-free vulnerability exists in the IPv6 raw socket handling code of Qualcomm Snapdragon chipsets. When the real device interface goes down and a route lookup is performed during raw IPv6 message transmission, the code attempts to access memory that has already been freed, leading to potential memory corruption and possible code execution.

MitigationApply the Qualcomm firmware patch (likely in a security update) to affected devices. Until the patch is available, avoid sending raw IPv6 messages on devices where the interface may go down, or implement network monitoring to detect interface state changes.

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
Apq8098 FirmwareOperating system
Affected:all versions
Mdm9206 FirmwareOperating system
Affected:all versions
Mdm9207c FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 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 chipset model
    Check the device or system documentation, or run commands like 'cat /proc/cpuinfo' on Linux-based embedded systems, or check bootloader/board identification strings
    Affected if The chipset matches one of: Apq8053, Apq8096au, Apq8098, Mdm9206, Mdm9207c, Mdm9607, Mdm9640, or Mdm9650
  2. Confirm firmware version
    Query the firmware version via manufacturer tools, bootloader info, or system information interfaces (such as 'getprop ro.build.id' on Android or 'cat /sys/firmware/devicetree/base/model' on embedded Linux)
    Affected if Any firmware version is present on the affected chipset models - all versions are vulnerable
  3. Identify raw IPv6 socket usage
    Audit running processes and applications for usage of raw sockets with protocol IPPROTO_RAW or IPPROTO_IPV6, and review application source code or network configuration for raw IPv6 transmission
    Affected if Applications or services are sending raw IPv6 packets on the device
  4. Test interface state change behavior
    While monitoring system logs (dmesg, /var/log/messages) and possibly running a raw IPv6 sender in a loop, bring down and up network interfaces (ip link set dev <iface> down/up) and observe for crashes, kernel panics, or memory corruption errors
    Affected if The system crashes, produces use-after-free kernel errors, or exhibits memory corruption when IPv6 raw sockets are active and an interface transitions to down state
  5. Check for relevant crashes in logs
    Review kernel logs, crash dumps, and system logs for symptoms such as 'use-after-free', 'raw socket', 'IPv6', or 'memory corruption' errors, particularly around network interface state changes
    Affected if Logs contain use-after-free errors or memory corruption traces related to IPv6 raw socket handling

A device is affected if it uses one of the listed Qualcomm chipset models and runs any firmware version while utilizing raw IPv6 sockets, with the vulnerability triggered when network interfaces change state.

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 Qualcomm firmware patch (likely in a security update) to affected devices. Until the patch is available, avoid sending raw IPv6 messages on devices where the interface may go down, or implement network monitoring to detect interface state changes.

Fix this in Apq8053 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-10603 — 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-10603 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