# CVE-2022-22096: Memory corruption in Snapdragon Connectivity, Snapdragon Mobile

> A stack-based buffer overflow in Qualcomm Bluetooth HOST allows attackers to execute arbitrary code or escalate privileges via crafted command length parameters.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** 3105585, A-213371834, ASB-A-213371834, GHSA-pcf8-p7p2-jgq9

## What is CVE-2022-22096?

CVE-2022-22096 is a critical memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 2 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory corruption in Bluetooth HOST due to stack-based buffer overflow when when extracting data using command length parameter in Snapdragon Connectivity, Snapdragon Mobile

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

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

It affects 57 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Sd460 Firmware, Qualcomm Sd480 Firmware, Qualcomm Sd662 Firmware, Qualcomm Sd665 Firmware, Qualcomm Sd675 Firmware, Qualcomm Sd678 Firmware, Qualcomm Sd680 Firmware, Qualcomm Sd690 5g Firmware, Qualcomm Sd695 Firmware, Qualcomm Sd720g Firmware, Qualcomm Sd730 Firmware, Qualcomm Sd765 Firmware, Qualcomm Sd765g Firmware, Qualcomm Sd768g Firmware, Qualcomm Sd778g Firmware, Qualcomm Sd780g Firmware, Qualcomm Sd855 Firmware and 37 more.

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

Apply the vendor's patch.

## Is CVE-2022-22096 being exploited?

There is no known exploitation of CVE-2022-22096 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-2021-35081](https://insights.sbomify.com/CVE-2021-35081/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22096 is a critical memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 2 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-22096 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-22096/ (Markdown: https://insights.sbomify.com/CVE-2022-22096/index.md)
```

## Sources

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

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