# CVE-2022-25721: Incorrect Type Conversion in Video driver

> Type confusion in Qualcomm video drivers allows memory corruption, potentially enabling code execution or privilege escalation on Android devices.

- **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:** Yes
- **Published:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** 3155019, A-238118629, GHSA-c4gj-hh7r-67qf, PUB-A-238118629

## What is CVE-2022-25721?

CVE-2022-25721 is a medium-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 6 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption in video driver due to type confusion error during video playback

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

It affects 45 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Mdm9150 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Qca6564 Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca8337 Firmware, Qualcomm Qcn9074 Firmware, Qualcomm Qcs410 Firmware, Qualcomm Qcs610 Firmware, Qualcomm Qcs8155 Firmware, Qualcomm Qualcomm215 Firmware, Qualcomm Sa6145p Firmware, Qualcomm Sa6150p Firmware, Qualcomm Sa6155p Firmware, Qualcomm Sa8145p Firmware and 25 more.

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

Apply the vendor's patch.

## Is CVE-2022-25721 being exploited?

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

What it is: CVE-2022-25721 is a medium-severity memory corruption vulnerability in Qualcomm Aqt1000 Firmware, published on 6 Jan 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-25721 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-25721/ (Markdown: https://insights.sbomify.com/CVE-2022-25721/index.md)
```

## Sources

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

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