# CVE-2022-33226: Buffer copy without checking the size of input in Core

> A buffer overflow in Qualcomm Snapdragon Core allows attackers to execute arbitrary code or escalate privileges via malicious ioctl commands.

- **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-c3v5-q6rv-gj3j

## What is CVE-2022-33226?

CVE-2022-33226 is a medium-severity memory corruption 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 buffer copy without checking the size of input in Core while processing ioctl commands from diag client applications.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 33 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 Sa8255p Firmware, Qualcomm Sd855 Firmware, Qualcomm Sm8150-Ac Firmware, Qualcomm Sm8150 Firmware, Qualcomm Sm8350-Ac Firmware, Qualcomm Sm8350 Firmware, Qualcomm Sm8450 Firmware, Qualcomm Snapdragon Wear 4100\+ Platform Firmware, Qualcomm Wcd9341 Firmware, Qualcomm Wcd9380 Firmware, Qualcomm Wcd9385 Firmware, Qualcomm Wcn3610 Firmware and 13 more.

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

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

## Is CVE-2022-33226 being exploited?

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

What it is: CVE-2022-33226 is a medium-severity memory corruption 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-33226 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-33226/ (Markdown: https://insights.sbomify.com/CVE-2022-33226/index.md)
```

## Sources

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

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