# CVE-2025-27038: Qualcomm Multiple Chipsets Use-After-Free

> A use-after-free flaw in Qualcomm Adreno GPU drivers allows attackers to execute arbitrary code or escalate privileges via malicious graphics rendering in Chrome on Android.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Jun 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** 4080397, A-418032173, ASB-A-418032173, GHSA-h454-pc9h-rvh2

## What is CVE-2025-27038?

CVE-2025-27038 is a high-severity use after free vulnerability in Qualcomm Ar8031 Firmware, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.

Weakness: CWE-416 (Use After Free)

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

It affects 44 products.


Products: Qualcomm Ar8031 Firmware, Qualcomm Csra6620 Firmware, Qualcomm Csra6640 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Qca2066 Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qcm6125 Firmware, Qualcomm Qcm8550 Firmware, Qualcomm Qcn9011 Firmware, Qualcomm Qcn9012 Firmware, Qualcomm Qcs6125 Firmware, Qualcomm Qcs8550 Firmware, Qualcomm Sm6475 Firmware, Qualcomm Sm6650 Firmware, Qualcomm Sm6650p Firmware, Qualcomm Sm7435 Firmware, Qualcomm Sm7635 Firmware, Qualcomm Sm7635p Firmware, Qualcomm Smart Audio 400 Platform Firmware, Qualcomm Snapdragon 4 Gen 2 Mobile Platform Firmware and 24 more.

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

Apply the vendor's patch. US federal agencies must fix it by 24 Jun 2025.

## Is CVE-2025-27038 being exploited?

Yes. Attackers have exploited CVE-2025-27038 in the wild since at least 3 Jun 2025.

## Other vulnerabilities in Qualcomm Ar8031 Firmware

- [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)
- [CVE-2021-30274](https://insights.sbomify.com/CVE-2021-30274/): Integer overflow in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27038 is a high-severity use after free vulnerability in Qualcomm Ar8031 Firmware, published on 3 Jun 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-27038 in the wild since at least 3 Jun 2025.

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-27038/ (Markdown: https://insights.sbomify.com/CVE-2025-27038/index.md)
```

## Sources

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

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