# CVE-2022-33214: Race condition in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

> A time-of-check time-of-use race condition in Qualcomm Snapdragon display metadata handling allows attackers to execute arbitrary code or escalate privileges.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Oct 2022
- **Updated:** 14 May 2025
- **Also known as:** 3178237, A-238103940, ASB-A-238103940, GHSA-xxgc-m52v-3qm3

## What is CVE-2022-33214?

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

### Official description

Memory corruption in display due to time-of-check time-of-use of metadata reserved size in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wearables

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 102 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qcc5100 Firmware, Qualcomm Qcm2290 Firmware, Qualcomm Qcm4290 Firmware, Qualcomm Qcm6125 Firmware, Qualcomm Qcm6490 Firmware, Qualcomm Qcn7606 Firmware, Qualcomm Qcs2290 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs4290 Firmware and 82 more.

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

Apply the vendor's patch.

## Is CVE-2022-33214 being exploited?

There is no known exploitation of CVE-2022-33214 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-33214 and fix it if it is affected.

What it is: CVE-2022-33214 is a high-severity vulnerability in Qualcomm Aqt1000 Firmware, published on 17 Oct 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-33214 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-33214/ (Markdown: https://insights.sbomify.com/CVE-2022-33214/index.md)
```

## Sources

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

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