# CVE-2022-33227: Double free in Linux-Android

> A double free vulnerability in Qualcomm Snapdragon Android components allows attackers to cause memory corruption, potentially leading to code execution or privilege escalation.

- **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:** 3 Aug 2024
- **Also known as:** GHSA-pgh3-m69x-g87p

## What is CVE-2022-33227?

CVE-2022-33227 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 in Linux android due to double free while calling unregister provider after register call.

Weakness: CWE-415 (Double Free)

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

It affects 71 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Qam8255p Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qca6310 Firmware, Qualcomm Qca6320 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qca6564 Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca6698aq Firmware, Qualcomm Qca6797aq Firmware and 51 more.

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

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

## Is CVE-2022-33227 being exploited?

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

What it is: CVE-2022-33227 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-33227 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-33227/ (Markdown: https://insights.sbomify.com/CVE-2022-33227/index.md)
```

## Sources

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

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