# CVE-2025-21480: Qualcomm Multiple Chipsets Incorrect Authorization

> Attackers can execute unauthorized GPU commands causing memory corruption, potentially leading to code execution or privilege escalation on Snapdragon devices.

- **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Jun 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-gj4f-pc42-qxg8

## What is CVE-2025-21480?

CVE-2025-21480 is a high-severity missing authorization vulnerability in Qualcomm Aqt1000 Firmware, published on 3 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 76 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 Qcm4490 Firmware, Qualcomm Qcs4490 Firmware, Qualcomm Sc8380xp Firmware, Qualcomm Sd855 Firmware, Qualcomm Sm4635 Firmware, Qualcomm Sm6250 Firmware, Qualcomm Sm6650 Firmware, Qualcomm Sm6650p Firmware, Qualcomm Sm7325p Firmware, Qualcomm Sm7635 Firmware, Qualcomm Sm7675 Firmware, Qualcomm Sm7675p Firmware, Qualcomm Sm8550p Firmware and 56 more.

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

No fix has been published for CVE-2025-21480 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 24 Jun 2025.

## Is CVE-2025-21480 being exploited?

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

## 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-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)
- [CVE-2021-35081](https://insights.sbomify.com/CVE-2021-35081/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-21480 is a high-severity missing authorization vulnerability in Qualcomm Aqt1000 Firmware, published on 3 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-21480 in the wild since at least 3 Jun 2025.

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

## Sources

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

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