dbcve.org
Aqt1000 FirmwareOperating system · Qualcomm

CVE-2022-22070

HIGH · 7.8 CVSS v3.1 Published 2022-09-02
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 in audio due to lack of check of invalid routing address into APR Routing table 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 · moderate confidence

Memory corruption vulnerability in Qualcomm Snapdragon audio subsystem where the APR (Audio Processor Routing) table lacks validation of routing addresses, allowing an invalid address to be processed and causing memory corruption. This could enable local privilege escalation or denial of service via crafted audio requests.

MitigationApply vendor firmware patches from Qualcomm and subsequent device manufacturer updates. Users should update affected devices to manufacturer-provided patched versions.

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
Aqt1000 FirmwareOperating system
Affected:all versions
Ar8031 FirmwareOperating system
Affected:all versions
Ar8035 FirmwareOperating system
Affected:all versions
Csra6620 FirmwareOperating system
Affected:all versions
Csra6640 FirmwareOperating system
Affected:all versions
Csrb31024 FirmwareOperating system
Affected:all versions
Mdm9150 FirmwareOperating system
Affected:all versions
Mdm9250 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 device audio subsystem
    Determine if the device uses a Qualcomm Snapdragon audio subsystem. Check device specifications, system information, or audio driver details for Qualcomm audio components.
    Affected if Device uses any Qualcomm Snapdragon audio hardware
  2. Identify exact Qualcomm audio chip model
    Check the specific Qualcomm audio chip/firmware model. This may be found in device firmware details, audio driver information, or system diagnostics. Look for model numbers: Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024, Mdm9150, or Mdm9250.
    Affected if Audio chip model matches any of: Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024, Mdm9150, or Mdm9250
  3. Check audio firmware version
    Query the audio subsystem firmware version through device diagnostics, audio driver APIs, or manufacturer-provided tools. Compare against the affected product list.
    Affected if Firmware version corresponds to any of the listed affected products (all versions are vulnerable)
  4. Verify APR audio processing is active
    Confirm that the device uses the Audio Processor Routing (APR) subsystem for audio processing. This is typically active on devices using Qualcomm audio firmware for audio playback, recording, or voice calls.
    Affected if Device processes audio through the Qualcomm APR subsystem
  5. Confirm absence of vendor patch
    Check if the device has received firmware updates from the device manufacturer. Review firmware changelogs or contact the device manufacturer to verify if CVE-2022-22070 has been addressed.
    Affected if No patch for CVE-2022-22070 has been applied to the audio firmware

The environment is affected if the device uses any of the listed Qualcomm audio firmware products (Aqt1000, Ar8031, Ar8035, Csra6620, Csra6640, Csrb31024, Mdm9150, Mdm9250) without the vendor security patch for this vulnerability.

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 vendor firmware patches from Qualcomm and subsequent device manufacturer updates. Users should update affected devices to manufacturer-provided patched versions.

Fix this in Aqt1000 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22070 — 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-22070 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