# CVE-2025-47318: Buffer Over-read in BT Controller

> A buffer over-read in the Bluetooth controller allows attackers to cause a transient denial of service via crafted EPTM test control messages.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-xrpv-r5rq-cxjp

## What is CVE-2025-47318?

CVE-2025-47318 is a high-severity denial of service vulnerability in Qualcomm Apq8017 Firmware, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Transient DOS while parsing the EPTM test control message to get the test pattern.

Weakness: CWE-126 (Buffer Over-read)

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

It affects 203 products.


Products: Qualcomm Apq8017 Firmware, Qualcomm Apq8064au Firmware, Qualcomm Aqt1000 Firmware, Qualcomm Ar8031 Firmware, Qualcomm Ar8035 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Csrb31024 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Flight Rb5 5g Platform Firmware, Qualcomm Home Hub 100 Platform Firmware, Qualcomm Immersive Home 214 Platform Firmware, Qualcomm Immersive Home 216 Platform Firmware, Qualcomm Immersive Home 316 Platform Firmware, Qualcomm Immersive Home 318 Platform Firmware, Qualcomm Ipq5010 Firmware and 183 more.

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

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

## Is CVE-2025-47318 being exploited?

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

## Other vulnerabilities in Qualcomm Apq8017 Firmware

- [CVE-2025-21483](https://insights.sbomify.com/CVE-2025-21483/): Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity (critical 9.8)
- [CVE-2021-1933](https://insights.sbomify.com/CVE-2021-1933/): Denial of service in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Wearables (critical 9.8)
- [CVE-2021-1946](https://insights.sbomify.com/CVE-2021-1946/): Null dereference in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11176](https://insights.sbomify.com/CVE-2020-11176/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)
- [CVE-2020-11291](https://insights.sbomify.com/CVE-2020-11291/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47318 is a high-severity denial of service vulnerability in Qualcomm Apq8017 Firmware, published on 24 Sep 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-47318 in the wild and no public exploit code.

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

## Sources

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

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