# CVE-2023-21667: Buffer Over-read in Bluetooth HOST

> A buffer over-read in the Bluetooth HOST component allows attackers to cause a transient denial of service on Android devices using Qualcomm Snapdragon chipsets.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2023
- **Updated:** 2 Aug 2024
- **Also known as:** 3306293, A-271904738, GHSA-p54g-g6xw-2jm9, PUB-A-271904738

## What is CVE-2023-21667?

CVE-2023-21667 is a medium-severity denial of service vulnerability in Qualcomm Qca6390 Firmware, published on 5 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Transient DOS in Bluetooth HOST while passing descriptor to validate the blacklisted BT keyboard.

Weakness: CWE-125 (Out-of-bounds Read), CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2023-21667?

It affects 43 products.


Products: Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qcc5100 Firmware, Qualcomm Qcn9074 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Sa6145p Firmware, Qualcomm Sa6150p Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8145p Firmware, Qualcomm Sa8150p Firmware, Qualcomm Sa8155p Firmware, Qualcomm Sa8195p Firmware, Qualcomm Sd865 5g Firmware, Qualcomm Sd870 Firmware and 23 more.

## How do I fix CVE-2023-21667?

Apply the vendor's patch.

## Is CVE-2023-21667 being exploited?

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

## Other vulnerabilities in Qualcomm Qca6390 Firmware

- [CVE-2021-30336](https://insights.sbomify.com/CVE-2021-30336/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Wearables (high 8.4)
- [CVE-2020-11156](https://insights.sbomify.com/CVE-2020-11156/): 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 Wired Infrastructure and Networking (high 8.1)
- [CVE-2023-21647](https://insights.sbomify.com/CVE-2023-21647/): Improper Input Validation in Bluetooth HOST (medium 6.5)
- [CVE-2021-30314](https://insights.sbomify.com/CVE-2021-30314/): Information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables (medium 6.2)
- [CVE-2019-10618](https://insights.sbomify.com/CVE-2019-10618/): Null dereference in Snapdragon Connectivity (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-21667 and fix it if it is affected.

What it is: CVE-2023-21667 is a medium-severity denial of service vulnerability in Qualcomm Qca6390 Firmware, published on 5 Sep 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-21667 in the wild and no public exploit code.

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

## Sources

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

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