dbcve.org
Ipq8074 FirmwareOperating system · Qualcomm

CVE-2019-10540

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-30
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 in WLAN NAN function due to lack of check of count value received in NAN availability attribute in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking in IPQ8074, MSM8996AU, QCA6174A, QCA6574AU, QCA8081, QCA9377, QCA9379, QCS404, QCS405, QCS605, SD 636, SD 665, SD 675, SD 712 / SD 710 / SD 670, SD 730, SD 820, SD 835, SD 845 / SD 850, SD 855, SD 8CX, SDA660, SDM630, SDM660, 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

Buffer overflow vulnerability in the WLAN NAN (Neighbor Awareness Networking) function. The issue stems from missing validation of the 'count' value in the NAN availability attribute, allowing specially crafted input to overflow a buffer and potentially execute arbitrary code.

MitigationApply vendor-supplied firmware updates for affected Snapdragon chipsets. Until patches are available, disable NAN/Neighbor Discovery functionality in wireless settings as a workaround.

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
Ipq8074 FirmwareOperating system
Affected:all versions
Msm8996au FirmwareOperating system
Affected:all versions
Qca6174a FirmwareOperating system
Affected:all versions
Qca6574au FirmwareOperating system
Affected:all versions
Qca8081 FirmwareOperating system
Affected:all versions
Qca9377 FirmwareOperating system
Affected:all versions
Qca9379 FirmwareOperating system
Affected:all versions
Qcs404 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 wireless chipset model
    Check the device specifications, kernel logs, or system info for the Qualcomm chipset identifier (ipq8074, msm8996au, qca6174a, qca6574au, qca8081, qca9377, qca9379, or qcs404)
    Affected if The device uses any of the listed affected chipset models
  2. Check the wireless firmware version
    Query the wireless firmware version via `iw version`, `wpa_supplicant -v`, or check `/proc/version` for kernel and firmware strings
    Affected if The firmware version cannot be determined or matches the affected chipset list
  3. Verify NAN feature status
    Inspect wireless configuration files (typically in `/etc/config/wireless`, `/etc/hostapd.conf`, or via `iw` commands like `iw dev <interface> info`) for NAN, 11s, or Neighbor Discovery settings
    Affected if NAN/Neighbor Awareness Networking is explicitly enabled in the wireless configuration
  4. Check for NAN-related service
    Look for NAN daemon processes (nanod, nan-daemon) or services via `ps aux | grep -i nan` and check if the NAN interface exists via `ip link show`
    Affected if A NAN-specific network interface or service is present and active
  5. Review system logs for NAN crashes
    Examine kernel logs (`dmesg`, `/var/log/messages`, `journalctl -k`) for NAN-related buffer overflow warnings, memory corruption errors, or unexpected reboots
    Affected if Logs contain NAN-related crashes, heap overflow warnings, or memory corruption entries

If the device incorporates any of the listed Qualcomm chipsets and has NAN functionality enabled, the environment is likely affected by this buffer overflow vulnerability.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates for affected Snapdragon chipsets. Until patches are available, disable NAN/Neighbor Discovery functionality in wireless settings as a workaround.

Recommended fix Moderate confidence
  1. Check Qualcomm's official security advisories and firmware release notes for CVE-2019-10540
  2. Contact the device manufacturer (而非Qualcomm) to obtain patched firmware for your specific device model
  3. Apply the manufacturer-provided firmware update that addresses the NAN buffer overflow vulnerability
  4. Verify the patch has been applied by checking the firmware version or using vendor verification tools
  5. For devices that are end-of-life and no longer receive updates, consider replacing the device with a newer model that has security support
Caveat Patching firmware may require device downtime and should be tested in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipq8074 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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