# CVE-2025-47316: Double Free in Video

> A double free vulnerability in Qualcomm Snapdragon firmware allows attackers to execute arbitrary code or escalate privileges via a race condition.

- **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:** 24 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-5mjx-cfhc-v8vm

## What is CVE-2025-47316?

CVE-2025-47316 is a high-severity use after free vulnerability in Qualcomm Aqt1000 Firmware, published on 24 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption due to double free when multiple threads race to set the timestamp store.

Weakness: CWE-415 (Double Free)

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

It affects 29 products.


Products: Qualcomm Aqt1000 Firmware, Qualcomm Fastconnect 6200 Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6420 Firmware, Qualcomm Qca6430 Firmware, Qualcomm Sc8380xp Firmware, Qualcomm Snapdragon 7c\+ Gen 3 Compute Firmware, Qualcomm Snapdragon 8c Compute Platform \(Sc8180x-Ad\) Firmware, Qualcomm Snapdragon 8cx Compute Platform \(Sc8180x-Aa\) Firmware, Qualcomm Snapdragon 8cx Compute Platform \(Sc8180x-Ab\) Firmware, Qualcomm Snapdragon 8cx Gen 2 5g Compute Platform \(Sc8180x-Ac\) Firmware, Qualcomm Snapdragon 8cx Gen 2 5g Compute Platform \(Sc8180x-Af\) Firmware, Qualcomm Snapdragon 8cx Gen 3 Compute Platform \(Sc8280xp-Ab\) Firmware, Qualcomm Snapdragon 8cx Gen 3 Compute Platform \(Sc8280xp-Bb\) Firmware, Qualcomm Wcd9340 Firmware, Qualcomm Wcd9341 Firmware and 9 more.

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

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

## Is CVE-2025-47316 being exploited?

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

What it is: CVE-2025-47316 is a high-severity use after free vulnerability in Qualcomm Aqt1000 Firmware, published on 24 Sep 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-47316 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-2025-47316/ (Markdown: https://insights.sbomify.com/CVE-2025-47316/index.md)
```

## Sources

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

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