dbcve.org
Apq8096 FirmwareOperating system · Qualcomm

CVE-2019-10546

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Buffer overflow can occur in WLAN firmware while parsing beacon/probe_response frames during roaming in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking in APQ8096, APQ8096AU, IPQ6018, IPQ8074, MDM9607, MDM9640, MDM9650, MSM8996AU, Nicobar, QCA6174A, QCA6574, QCA6574AU, QCA6584, QCA6584AU, QCA8081, QCA9377, QCA9379, QCS404, QCS605, Rennell, SA6155P, SC8180X, SDA660, SDA845, SDM630, SDM636, SDM660, SDM670, SDM710, SDM845, SDM850, 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

Buffer overflow vulnerability in Qualcomm Snapdragon WLAN firmware when parsing beacon/probe_response frames during roaming. The overflow occurs in the firmware layer and could allow remote code execution or denial of service via specially crafted wireless frames.

MitigationApply vendor firmware updates from Qualcomm or device manufacturers for affected Snapdragon chipsets. Until patches are available, limit device exposure to untrusted networks and monitor for suspicious roaming behavior.

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
Apq8096 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Ipq6018 FirmwareOperating system
Affected:all versions
Ipq8074 FirmwareOperating system
Affected:all versions
Mdm9607 FirmwareOperating system
Affected:all versions
Mdm9640 FirmwareOperating system
Affected:all versions
Mdm9650 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 hardware specifications, system information, or bootloader output to determine the exact Qualcomm Snapdragon or modem chipset model in use (e.g., Apq8096, Ipq6018, Mdm9607)
    Affected if The chipset matches any of the following: Apq8096, Apq8096au, Ipq6018, Ipq8074, Mdm9607, Mdm9640, Mdm9650, or Msm8996au
  2. Confirm WLAN firmware version
    Access the device's WLAN firmware or radio firmware information through debug logs, diagnostic interfaces, or manufacturer-provided tools. Query the WLAN driver or firmware version string via commands like 'iw dev', 'wlan_cli', or vendor-specific AT commands if available
    Affected if The WLAN firmware version cannot be determined or is present on an affected chipset (all versions of the listed firmwares are vulnerable)
  3. Verify WLAN interface is enabled
    Check if the WLAN interface is active using commands such as 'ip link show', 'iwconfig', or 'wlanutil'. Look for wireless interfaces (e.g., wlan0, wlp*) in the system
    Affected if WLAN is enabled and the device is using the affected chipset firmware
  4. Check roaming configuration
    Inspect the wireless configuration files (e.g., wpa_supplicant.conf, hostapd.conf) or network manager settings for roaming-enabled profiles. Look for parameters like 'roaming', 'fast_reassoc', or802.11k/802.11v settings
    Affected if Roaming is enabled or the device is configured to connect to multiple access points (the vulnerability triggers during beacon/probe_response frame parsing during roaming)

A device is affected if it contains any of the listed Qualcomm chipsets (Apq8096, Apq8096au, Ipq6018, Ipq8074, Mdm9607, Mdm9640, Mdm9650, Msm8996au) with WLAN functionality enabled, since all firmware versions for these chipsets are vulnerable to the buffer overflow during roaming operations.

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 firmware updates from Qualcomm or device manufacturers for affected Snapdragon chipsets. Until patches are available, limit device exposure to untrusted networks and monitor for suspicious roaming behavior.

Fix this in Apq8096 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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