CVE-2020-11147
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 · uneditedUse after free issue in audio modules while removing and freeing objects during list iteration due to incorrect usage of macro in Snapdragon Compute, Snapdragon Industrial IOT, Snapdragon Mobile
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 · moderate confidenceA use-after-free vulnerability exists in audio modules of Qualcomm Snapdragon chips. The flaw occurs when removing and freeing objects during list iteration due to incorrect macro usage, causing memory to be accessed after being freed.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 PMIC/audio module model in useCheck system hardware information or device tree to determine the specific Qualcomm PMIC firmware component (such as Pm3003a, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l, Pm6250, or Aqt1000) present in the deviceAffected if The device contains any of the listed affected PMIC firmware components (Aqt1000, Pm3003a, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l, or Pm6250)
-
Check the installed firmware versionAccess the PMIC or audio subsystem firmware version through vendor-specific interfaces (such as debug logs, /sys nodes, or hardware diagnostic tools provided by the OEM)Affected if The firmware version matches any of the affected products listed (all versions of Aqt1000, Pm3003a, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l, or Pm6250 firmware)
-
Verify audio module is activeCheck if the audio subsystem using the affected Qualcomm audio module is enabled and running on the deviceAffected if The audio module is actively processing and the device uses one of the affected PMIC/audio firmware components
A device is affected if it contains any of the listed Qualcomm PMIC/audio firmware components (Aqt1000, Pm3003a, Pm456, Pm6125, Pm6150, Pm6150a, Pm6150l, or Pm6250) regardless of version, since all versions are vulnerable.
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 dataThis is a firmware-level vulnerability requiring a patch from the device/vendor. Users should apply vendor firmware updates as they become available for affected Snapdragon Compute, Industrial IOT, and Mobile products.
- 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-2020-11147 — 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-2020-11147 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