# CVE-2022-33290: Null pointer dereference in Bluetooth HOST

> A null pointer dereference in the Bluetooth HOST component of Qualcomm Snapdragon chipsets allows attackers to cause a transient denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-f73m-w3jg-64qm

## What is CVE-2022-33290?

CVE-2022-33290 is a high-severity vulnerability in Qualcomm Apq8017 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

Transient DOS in Bluetooth HOST due to null pointer dereference when a mismatched argument is passed.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 46 products.


Products: Qualcomm Apq8017 Firmware, Qualcomm Apq8096au Firmware, Qualcomm Ar8031 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Mdm9206 Firmware, Qualcomm Mdm9250 Firmware, Qualcomm Mdm9607 Firmware, Qualcomm Mdm9628 Firmware, Qualcomm Mdm9640 Firmware, Qualcomm Mdm9650 Firmware, Qualcomm Msm8996au Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6175a Firmware, Qualcomm Qca6564a Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574 Firmware and 26 more.

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

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

## Is CVE-2022-33290 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8017 Firmware

- [CVE-2025-21483](https://insights.sbomify.com/CVE-2025-21483/): Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity (critical 9.8)
- [CVE-2021-1933](https://insights.sbomify.com/CVE-2021-1933/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-1946](https://insights.sbomify.com/CVE-2021-1946/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11176](https://insights.sbomify.com/CVE-2020-11176/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11291](https://insights.sbomify.com/CVE-2020-11291/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33290 is a high-severity vulnerability in Qualcomm Apq8017 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-33290 in the wild and no public exploit code.

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

## Sources

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

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