CVE-2022-22090
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 · uneditedMemory corruption in audio due to use after free while managing buffers from internal cache in Snapdragon Compute, Snapdragon Connectivity, 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 confidenceUse-after-free vulnerability in the audio component of Qualcomm Snapdragon chipsets. The vulnerability occurs when managing buffers from an internal cache, leading to memory corruption that could allow local privilege escalation 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 modelCheck the device specifications or use commands like 'cat /proc/cpuinfo' on Android or check system information on other embedded devices to determine the Snapdragon or Qualcomm chipset variant (e.g., SM8475, SD888)Affected if The chipset model matches one of the affected products: Sd 8 Gen1 5g, Sd865 5g, Sd888 5g, Sdx65, Sm7450, Sm8475, Sm8475p, or Wcd9370
-
Check audio subsystem firmware versionQuery the audio component firmware version through vendor-specific diagnostic tools, system logs (dmesg, logcat), or by reading /sys/firmware or /vendor/firmware partition entries related to audio codecs (wcd9370 or similar audio DSP firmware files)Affected if The audio firmware version is present and matches the affected chipset list, indicating the unpatched firmware is in use
-
Verify audio service exposureCheck if audio-related services (such as audio-hal, audio-dsp, or vendor audio daemons) are running and accessible to local applications via 'ps -A | grep audio' or similar process listing toolsAffected if Audio services are active on an affected chipset, creating the attack surface for the use-after-free in buffer management
-
Check for available security patchesReview the device or system firmware changelog/vendor advisories to determine if the CVE-2022-22090 patch has been applied to the audio componentAffected if The installed firmware lacks the security patch for CVE-2022-22090, meaning the use-after-free vulnerability remains unmitigated
The device is affected if it uses any of the listed Qualcomm chipsets (Sd 8 Gen1 5g, Sd865 5g, Sd888 5g, Sdx65, Sm7450, Sm8475, Sm8475p, Wcd9370) and the audio firmware has not been updated to include the CVE-2022-22090 security patch.
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 security patches released by Qualcomm and downstream device manufacturers for affected Snapdragon Compute, Connectivity, and Mobile platforms.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22090 — 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-2022-22090 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