CVE-2022-22089
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 while playing record due to improper list handling in two threads in Snapdragon Connectivity, Snapdragon Mobile, Snapdragon Wearables
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 confidenceMemory corruption vulnerability in Qualcomm Snapdragon audio component caused by improper list handling between two threads during audio playback/recording. This race condition in thread synchronization leads to potential memory corruption, likely due to concurrent access to shared data structures without proper locking mechanisms.
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 chip model in your deviceCheck device specifications, system information, or firmware details to determine the exact Qualcomm Snapdragon or Qualcomm networking chip model (e.g., via `lspci`, `cat /proc/cpuinfo`, or device BIOS/UEFI)Affected if The chip model matches one of: Ar8035, Qca8081, Qca8337, Sd 8 Gen1 5g, Sdx65, Sm7450, Sm8475, or Sm8475p
-
Locate the firmware version for the identified Qualcomm componentQuery the firmware version through vendor-specific tools, device management interfaces, or system firmware tables (e.g., via `dmidecode`, vendor diagnostic utilities, or network switch management interfaces for networking chips)Affected if The device runs any firmware version on the affected chip models (all versions are vulnerable)
-
Determine if the audio playback or recording functionality is activeMonitor process activity or system logs related to audio services (e.g., ALSA, PulseAudio, or vendor audio daemons) to confirm audio I/O operations are occurringAffected if Audio playback or recording is actively being performed on the device, triggering the vulnerable code path
If your device contains any of the listed Qualcomm chip models (Ar8035, Qca8081, Qca8337, Sd 8 Gen1 5g, Sdx65, Sm7450, Sm8475, Sm8475p) and uses audio functionality, the environment is affected by this 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 vendor-supplied firmware/security updates from Qualcomm and device OEMs. This is a client-side vulnerability requiring firmware updates for affected Snapdragon-based devices.
- Consultation4.0 h
- Implementation2.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22089 — 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-22089 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