CVE-2022-22081
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 module due to integer overflow in Snapdragon Auto, 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 confidenceInteger overflow in the audio module of Qualcomm Snapdragon chips allows memory corruption. The vulnerability stems from insufficient bounds checking on integer values, which can be manipulated to cause buffer overflows or out-of-bounds memory writes in the audio processing component.
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 Snapdragon chip modelCheck the device specifications or system information to determine the exact Snapdragon chipset model (e.g., via device info settings, /proc/cpuinfo on Android, or system firmware logs)Affected if The chip model matches any of: Ar8035, Qca6595au, Qca8081, Qca8337, Sa6155p, Sa8155p, Sa8195p, or SD 8 Gen1 5g
-
Determine the audio firmware versionAccess the audio module firmware version through the device's service menu, diagnostic logs, or by querying the audio subsystem (e.g., via adb shell dumpsys audio, or checking /vendor/firmware/ for audio-related firmware files)Affected if The audio firmware version is present and corresponds to the affected chip models (all versions of these chips are vulnerable)
-
Verify the audio processing component is activeCheck if the audio HAL (Hardware Abstraction Layer) or audio daemon is running and processing audio data (e.g., via process list, service status, or audio hardware state)Affected if The audio module is actively processing audio files or streams, which triggers the vulnerable code path
-
Check for accessible audio input/output interfacesInspect whether the device exposes audio interfaces (e.g., microphone, speaker, Bluetooth audio) that exercise the vulnerable audio processing componentAffected if Any audio input or output functionality is enabled and accessible on the device
A device is affected if it uses any of the listed Qualcomm Snapdragon chip models (Ar8035, Qca6595au, Qca8081, Qca8337, Sa6155p, Sa8155p, Sa8195p, or SD 8 Gen1 5g) and has the audio processing component active, since all firmware versions of these chips are vulnerable to the integer overflow in the audio module.
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 patches from Qualcomm//device OEMs. Prioritize updating mobile devices, wearables, and automotive systems using affected Snapdragon chipsets.
- Consultation8.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 $6,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22081 — 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-22081 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