dbcve.org
Apq8009 FirmwareOperating system · Qualcomm

CVE-2022-22082

HIGH · 7.8 CVSS v3.1 Published 2022-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Memory corruption due to possible buffer overflow while parsing DSF header with corrupted channel count in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, 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 · high confidence

Buffer overflow vulnerability in DSF (Digital Stream Format) header parsing logic where a corrupted channel count value is not properly validated, leading to memory corruption. This is a memory corruption issue in the media/audio processing component affecting multiple Snapdragon chip families used in automotive, compute, mobile, IoT, and wearable devices.

MitigationApply firmware updates from device OEMs that include the patched Qualcomm software addressing the DSF header parsing vulnerability. Users should update their devices to the latest firmware version provided by their manufacturer.

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 data
Apq8009 FirmwareOperating system
Affected:all versions
Apq8009w FirmwareOperating system
Affected:all versions
Apq8017 FirmwareOperating system
Affected:all versions
Apq8053 FirmwareOperating system
Affected:all versions
Apq8096au FirmwareOperating system
Affected:all versions
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Qualcomm chipset model
    Check /proc/cpuinfo, lspci, or device tree files in /sys/firmware/devicetree/base to identify the Qualcomm APQ or AQ series chip present in the device
    Affected if The device uses any of the following chips: Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, or Csra6620
  2. Check firmware version
    Retrieve firmware version from /vendor/firmware directory, /etc/firmware, or via vendor-specific commands such as 'getprop' on Android or 'cat /sys/class/firmware/.../version'
    Affected if The firmware version cannot be verified as patched or the device is running any version of the affected firmware
  3. Identify DSF audio processing component
    Search for audio processing libraries or services that handle DSF (Digital Stream Format) files, commonly found in audio daemon logs, library paths like /vendor/lib/, or audio server configurations
    Affected if The device has software components capable of parsing DSF audio file headers present in the system
  4. Check for audio processing usage
    Monitor or inspect active audio processes and services (such as audio daemon, media server, or Bluetooth audio stack) that may invoke DSF parsing functionality
    Affected if Any audio processing service is actively running that could invoke the vulnerable DSF header parsing code path
  5. Review audio codec configuration
    Examine audio codec configuration files and registered codecs in /etc/audio_policy.conf, audio_effects.conf, or vendor-specific audio configuration to identify if DSF format support is enabled
    Affected if DSF format is listed as a supported audio format in the system's audio codec or format configuration

The device is affected if it contains any of the listed Qualcomm chipsets (Apq8009, Apq8009w, Apq8017, Apq8053, Apq8096au, Aqt1000, Ar8031, Csra6620) and has DSF audio parsing functionality enabled or accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates from device OEMs that include the patched Qualcomm software addressing the DSF header parsing vulnerability. Users should update their devices to the latest firmware version provided by their manufacturer.

Fix this in Apq8009 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22082 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22082 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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