CVE-2021-1915
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 · uneditedBuffer overflow can occur due to improper validation of NDP application information length 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
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 confidenceBuffer overflow vulnerability in Qualcomm Snapdragon chipsets caused by improper validation of NDP (Neighbor Discovery Protocol) application information length. The lack of proper bounds checking on length fields allows specially crafted network packets to overflow buffers, potentially leading to arbitrary code execution or denial of service.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset or firmwareDetermine the specific Qualcomm chipset model or firmware installed on the device. This may be visible in system information, device specifications, or firmware build details. Common locations include /proc/cpuinfo on embedded Linux systems, bootloader information, or vendor documentation.Affected if The detected chipset or firmware matches any of: Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, or Csra6640
-
Check if NDP (Neighbor Discovery Protocol) is enabledVerify whether the device has NDP functionality enabled. On Linux systems, this can be checked via ip -6 neigh show, sysctl net.ipv6.conf.all.forwarding, or by examining if IPv6 neighbor discovery is actively used. On other platforms, check network stack configuration for IPv6 Neighbor Discovery capabilities.Affected if NDP is enabled and the device processes IPv6 neighbor discovery traffic
-
Determine if network packet processing handles NDP application informationInspect network configuration or capture network traffic to see if the device processes NDP application layer information. This may involve reviewing packet capture files (PCAP) or monitoring for NDP-related network activity.Affected if The device receives and processes NDP packets containing application information
-
Review firmware version against vendor releasesCompare the installed firmware version against any patches released by the device manufacturer. Note that all versions of the listed products are affected, so any unpatched firmware version would be vulnerable.Affected if The installed firmware is any version that has not been patched by the OEM to address this vulnerability
If the device uses any of the listed Qualcomm firmware products (Apq8096au, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811, Csra6620, or Csra6640) and has NDP/IPv6 neighbor discovery enabled, it is likely affected by this buffer overflow vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply firmware/security patches released by device manufacturers (OEMs) that incorporate Qualcomm's updated firmware addressing the NDP validation flaw. Users should check with their device vendors for available updates.
- Consultation8.0 h
- Implementation4.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-1915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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