# CVE-2022-22070: Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

> Memory corruption in Qualcomm Snapdragon audio routing allows attackers to execute arbitrary code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-ghjx-g5f9-8w23

## What is CVE-2022-22070?

CVE-2022-22070 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 2 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-22070?

It affects 145 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6175a Firmware, Qualcomm Qca6310 Firmware, Qualcomm Qca6320 Firmware, Qualcomm Qca6335 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6421 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6430 Firmware and 125 more.

## How do I fix CVE-2022-22070?

No fix has been published for CVE-2022-22070 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-22070 being exploited?

There is no known exploitation of CVE-2022-22070 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Aqt1000 Firmware

- [CVE-2025-21479](https://insights.sbomify.com/CVE-2025-21479/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2025-21480](https://insights.sbomify.com/CVE-2025-21480/): Qualcomm Multiple Chipsets Incorrect Authorization (high 8.6, exploited in the wild)
- [CVE-2023-28562](https://insights.sbomify.com/CVE-2023-28562/): Buffer Copy Without Checking Size of Input in QESL (critical 9.8)
- [CVE-2022-40514](https://insights.sbomify.com/CVE-2022-40514/): Buffer copy without checking size of input in WLAN Firmware (critical 9.8)
- [CVE-2022-22096](https://insights.sbomify.com/CVE-2022-22096/): Memory corruption in Snapdragon Connectivity, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22070 and fix it if it is affected.

What it is: CVE-2022-22070 is a high-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 2 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22070 in the wild and no public exploit code.

Affected product: Qualcomm Aqt1000 Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-22070/ (Markdown: https://insights.sbomify.com/CVE-2022-22070/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-22070
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-22070
- OSV: https://osv.dev/vulnerability/CVE-2022-22070

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-22070/
Summaries are generated and may contain mistakes; the official description above is the record.