# CVE-2025-27071: Buffer Copy Without Checking Size of Input in Powerline Communication Firmware

> Memory corruption in Qualcomm Snapdragon Powerline Communication Firmware allows attackers to execute arbitrary code or escalate privileges via crafted files.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-3ff3-h6c4-m2xr

## What is CVE-2025-27071?

CVE-2025-27071 is a high-severity memory corruption vulnerability in Qualcomm Fastconnect 6800 Firmware, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Memory corruption while processing specific files in Powerline Communication Firmware.

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

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

It affects 34 products.


Products: Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6426 Firmware, Qualcomm Qca6436 Firmware, Qualcomm Qsm8250 Firmware, Qualcomm Sd865 5g Firmware, Qualcomm Sdm429w Firmware, Qualcomm Sdx55 Firmware, Qualcomm Snapdragon 429 Mobile Platform Firmware, Qualcomm Snapdragon 865\+ 5g Mobile Platform \(Sm8250-Ab\) Firmware, Qualcomm Snapdragon 865 5g Mobile Platform Firmware, Qualcomm Snapdragon 870 5g Mobile Platform \(Sm8250-Ac\) Firmware, Qualcomm Snapdragon 8 Gen 1 Mobile Platform Firmware, Qualcomm Snapdragon W5\+ Gen 1 Wearable Platform Firmware, Qualcomm Snapdragon X55 5g Modem-Rf System Firmware, Qualcomm Snapdragon Xr2 5g Platform Firmware, Qualcomm Sw5100 Firmware, Qualcomm Sw5100p Firmware and 14 more.

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

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

## Is CVE-2025-27071 being exploited?

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

## Other vulnerabilities in Qualcomm Fastconnect 6800 Firmware

- [CVE-2023-28581](https://insights.sbomify.com/CVE-2023-28581/): Improper Restriction of Operations within the Bounds of a Memory Buffer in WLAN Firmware (critical 9.8)
- [CVE-2025-27037](https://insights.sbomify.com/CVE-2025-27037/): Use After Free in Camera Driver (high 7.8)
- [CVE-2025-21455](https://insights.sbomify.com/CVE-2025-21455/): Time-of-check Time-of-use (TOCTOU) Race Condition in Camera_Linux (high 7.8)
- [CVE-2025-21474](https://insights.sbomify.com/CVE-2025-21474/): Use After Free in BTHOST (high 7.8)
- [CVE-2024-45566](https://insights.sbomify.com/CVE-2024-45566/): Use After Free in Camera Driver (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27071 is a high-severity memory corruption vulnerability in Qualcomm Fastconnect 6800 Firmware, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27071 in the wild and no public exploit code.

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

## Sources

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

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