# CVE-2022-25663: Memory corruption in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity

> A buffer overflow in Snapdragon connectivity firmware allows attackers to cause a denial of service via management frame handling.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2022
- **Updated:** 15 May 2025
- **Also known as:** GHSA-mxwg-58m3-frx5

## What is CVE-2022-25663?

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

### Official description

Possible buffer overflow due to lack of buffer length check during management frame Rx handling lead to denial of service in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 31 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Qca1062 Firmware, Qualcomm Qca1064 Firmware, Qualcomm Qca2062 Firmware, Qualcomm Qca2064 Firmware, Qualcomm Qca2065 Firmware, Qualcomm Qca2066 Firmware, Qualcomm Qca6390 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Sd778g Firmware, Qualcomm Sd7c Firmware, Qualcomm Sd850 Firmware, Qualcomm Sd 8cx Gen2 Firmware, Qualcomm Sd 8cx Gen3 Firmware, Qualcomm Sm6250 Firmware, Qualcomm Wcd9340 Firmware, Qualcomm Wcd9341 Firmware, Qualcomm Wcd9380 Firmware and 11 more.

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

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

## Is CVE-2022-25663 being exploited?

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

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

## Sources

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

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