CVE-2021-30351
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 · uneditedAn out of bound memory access can occur due to improper validation of number of frames being passed during music playback in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, 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 confidenceAn out-of-bounds memory access vulnerability exists in Qualcomm Snapdragon chipsets due to improper validation of frame counts during music playback. The vulnerability allows memory corruption by providing a malicious number of frames to the audio subsystem, potentially leading to arbitrary code execution with kernel-level privileges.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm chipset model in your device or systemCheck system information or device specifications to determine if the chipset is one of the following: Apq8009, Apq8009w, Apq8017, Aqt1000, Ar8031, Ar8035, Ar9380, or Csr8811. This may require checking /proc/cpuinfo on Linux, device manager on Windows, or firmware/datasheet documentation.Affected if The chipset matches any of the affected models listed above.
-
Determine the firmware version of the Qualcomm audio subsystemQuery the audio driver or firmware version through available diagnostic interfaces. On Android, this may be accessible via 'getprop' or audio-specific debug logs. On embedded systems, check /sys/class/audio or vendor-specific diagnostic tools.Affected if The firmware version cannot be determined or is present on an affected chipset model.
-
Verify if audio playback functionality is exposedCheck if the device or system exposes audio playback capabilities that process media files. Look for audio daemon processes (such as audioflinger, audioserver, or vendor audio services) and confirm they are running.Affected if Audio playback functionality is available and the underlying chipset is one of the affected models.
-
Check for vendor firmware update availabilityConsult the device manufacturer or Qualcomm's product security advisories to determine if a firmware patch addressing CVE-2021-30351 has been released for your specific device and chipset version.Affected if No vendor security patch for CVE-2021-30351 has been applied to the affected chipset firmware.
A user is affected if their device or system uses any of the listed Qualcomm chipset models (Apq8009, Apq8009w, Apq8017, Aqt1000, Ar8031, Ar8035, Ar9380, Csr8811) and the audio subsystem with unpatched firmware is active.
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 vendor firmware updates from Qualcomm or device manufacturers that address this vulnerability. The fix requires correcting the input validation logic in the audio playback code to properly validate frame counts before performing memory operations.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA16.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30351 — 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-30351 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