# CVE-2022-33263: Use after free in Core

> A use-after-free vulnerability in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via DCI client interactions.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2023
- **Updated:** 7 Jan 2025
- **Also known as:** GHSA-qjww-gpp2-8qh6

## What is CVE-2022-33263?

CVE-2022-33263 is a medium-severity use after free vulnerability in Qualcomm Aqt1000 Firmware, published on 6 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption due to use after free in Core when multiple DCI clients register and deregister.

Weakness: CWE-416 (Use After Free)

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

It affects 49 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Qam8255p Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6698aq Firmware, Qualcomm Qca6797aq Firmware, Qualcomm Qcs8155 Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8155p Firmware, Qualcomm Sa8195p Firmware, Qualcomm Sa8255p Firmware, Qualcomm Sd855 Firmware, Qualcomm Sd 8 Gen1 5g Firmware, Qualcomm Sm4450 Firmware, Qualcomm Sm8150-Ac Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8350-Ac Firmware, Qualcomm Sm8350 Firmware and 29 more.

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

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

## Is CVE-2022-33263 being exploited?

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

What it is: CVE-2022-33263 is a medium-severity use after free vulnerability in Qualcomm Aqt1000 Firmware, published on 6 Jun 2023. 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-33263 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-33263/ (Markdown: https://insights.sbomify.com/CVE-2022-33263/index.md)
```

## Sources

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

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