# CVE-2025-47321: Buffer Copy Without Checking Size of Input in Core Services

> A buffer overflow in Qualcomm Snapdragon core services allows attackers to corrupt memory via crafted packets from unix clients, potentially leading to code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 18 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-hg2m-cjh9-f76f

## What is CVE-2025-47321?

CVE-2025-47321 is a high-severity memory corruption vulnerability in Qualcomm Ar8031 Firmware, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption while copying packets received from unix clients.

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

## Which versions are affected by CVE-2025-47321?

It affects 115 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Qam8255p Firmware, Qualcomm Qam8650p Firmware, Qualcomm Qam8775p Firmware, Qualcomm Qamsrv1h Firmware, Qualcomm Qamsrv1m Firmware, Qualcomm Qca2066 Firmware, Qualcomm Qca6174a Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6574 Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6595au Firmware and 95 more.

## How do I fix CVE-2025-47321?

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

## Is CVE-2025-47321 being exploited?

There is no known exploitation of CVE-2025-47321 in the wild and no public exploit code.

## Other vulnerabilities in Qualcomm Ar8031 Firmware

- [CVE-2025-27038](https://insights.sbomify.com/CVE-2025-27038/): Qualcomm Multiple Chipsets Use-After-Free (high 7.5, exploited in the wild)
- [CVE-2022-25729](https://insights.sbomify.com/CVE-2022-25729/): Improper Input Validation in MODEM (critical 9.8)
- [CVE-2022-25727](https://insights.sbomify.com/CVE-2022-25727/): Memory corruption in Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music (critical 9.8)
- [CVE-2021-30285](https://insights.sbomify.com/CVE-2021-30285/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)
- [CVE-2021-30275](https://insights.sbomify.com/CVE-2021-30275/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47321 and fix it if it is affected.

What it is: CVE-2025-47321 is a high-severity memory corruption vulnerability in Qualcomm Ar8031 Firmware, published on 18 Dec 2025. 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-2025-47321 in the wild and no public exploit code.

Affected product: Qualcomm Ar8031 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-2025-47321/ (Markdown: https://insights.sbomify.com/CVE-2025-47321/index.md)
```

## Sources

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

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