# CVE-2022-22088: Integer Overflow to Buffer Overflow in Bluetooth HOST

> An integer overflow in Qualcomm Bluetooth HOST allows remote attackers to trigger a buffer overflow, potentially leading to code execution or privilege escalation on Android devices.

- **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:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** 3052411, A-231156521, ASB-A-231156521, GHSA-2rj9-9w62-f3q6

## What is CVE-2022-22088?

CVE-2022-22088 is a critical vulnerability in Qualcomm Apq8009 Firmware, published on 6 Jan 2023. 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 buffer overflow while parsing the command response received from remote

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

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

It affects 150 products.


Products: Qualcomm Apq8009 Firmware, Qualcomm Apq8009w Firmware, Qualcomm Apq8052 Firmware, Qualcomm Apq8056 Firmware, Qualcomm Apq8076 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Msm8108 Firmware, Qualcomm Msm8208 Firmware, Qualcomm Msm8209 Firmware, Qualcomm Msm8608 Firmware, Qualcomm Msm8909w Firmware, Qualcomm Msm8952 Firmware, Qualcomm Msm8956 Firmware, Qualcomm Msm8976 Firmware, Qualcomm Msm8976sg Firmware, Qualcomm Msm8996au Firmware and 130 more.

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

Apply the vendor's patch.

## Is CVE-2022-22088 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8009 Firmware

- [CVE-2021-1905](https://insights.sbomify.com/CVE-2021-1905/): Qualcomm Multiple Chipsets Use-After-Free (high 8.4, exploited in the wild)
- [CVE-2020-11261](https://insights.sbomify.com/CVE-2020-11261/): Qualcomm Multiple Chipsets Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2021-1906](https://insights.sbomify.com/CVE-2021-1906/): Qualcomm Multiple Chipsets Detection of Error Condition Without Action (medium 6.2, exploited in the wild)
- [CVE-2022-40510](https://insights.sbomify.com/CVE-2022-40510/): Buffer copy without checking size of input in Audio. (critical 9.8)
- [CVE-2022-25720](https://insights.sbomify.com/CVE-2022-25720/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22088 is a critical vulnerability in Qualcomm Apq8009 Firmware, published on 6 Jan 2023. 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-22088 in the wild and no public exploit code.

Affected product: Qualcomm Apq8009 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-22088/ (Markdown: https://insights.sbomify.com/CVE-2022-22088/index.md)
```

## Sources

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

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