CVE-2025-21479: Qualcomm Multiple Chipsets Incorrect Authorization Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.
Description quoted from the CVE record (assigned by qualcomm, published 2025-06-03).
Weakness: CWE-863: Incorrect Authorization
How it can be exploited
Exploitable with local access with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.
- On CISA KEV since
- 2025-06-03
- US federal deadline
- 2025-06-24
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2025-06374, CNNVD-202506-177, EUVD-2025-16710, GHSA-vmqr-hrfr-7527
VEDAS cluster: VEDAS:BEBOOPBOLT
Exploit Observer links 12 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (12)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://github.com/7678837-glitch/lenovo_y700_tb320fc_on_cve-2025-21479
- Code repository: https://github.com/camsshaft/selinux-permissive-only-cve-2025-21479
- Code repository: https://github.com/diyiqiuye/cve-2025-21479-fx3
- Code repository: https://github.com/diyiqiuye/cve-2025-21479-fx5p
- Code repository: https://github.com/linux-tools/vivo_iqoo_neo_9_root_research_on_cve-2025-21479
- Code repository: https://github.com/longg66/cve-2025-21479_iqooneo7speed
- Code repository: https://github.com/qingizi7/cve-2025-21479_iqooneo8
- Code repository: https://github.com/reaizuguo/vivo_iqoo_neo_9_root_research_on_cve-2025-21479
- Code repository: https://github.com/shiho-patch/linux-tools-vivo_iqoo_neo_9_root_research_on_cve-2025-21479
- Code repository: https://github.com/type010/cve-2025-21479-iqoo11pro
- Code repository: https://github.com/xianwan1314/cve-2025-21479-iqoo11pro
- Code repository: https://github.com/xjoker/lenovo_y700_tb320fc_on_cve-2025-21479
Research and write-ups (1)
- Research or write-up: https://dawnslab.jd.com/android_gpu_attack_cve_2025_21479
Vulnerability databases and vendor advisories (5)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2025-16710
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-vmqr-hrfr-7527
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-21479
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-21479
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202506-177
89 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.008
low predicted chance of attack - VEDAS
- 0.978
strong exploit evidence - On CISA KEV
- Yes, since 2025-06-03
- Detection rule
- Out of scope (local)
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Qualcomm, Inc. Snapdragon | version AQT1000 version FastConnect 6200 version FastConnect 6700 version FastConnect 6800 version FastConnect 6900 version FastConnect 7800 version QCA6391 version QCM4490 and 67 more ranges | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: qualcomm snapdragon_460_mobile_platform_firmware, qualcomm snapdragon_480\+_5g_mobile_platform_\(sm4350-ac\)_firmware, qualcomm snapdragon_480_5g_mobile_platform_firmware, qualcomm snapdragon_4_gen_1_mobile_platform_firmware, qualcomm snapdragon_662_mobile_platform_firmware, qualcomm snapdragon_680_4g_mobile_platform_firmware, qualcomm snapdragon_685_4g_mobile_platform_\(sm6225-ad\)_firmware, qualcomm snapdragon_690_5g_mobile_platform_firmware, qualcomm snapdragon_695_5g_mobile_platform_firmware, qualcomm snapdragon_720g_mobile_platform_firmware.
How to fix it
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor guidance:
- https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html
- https://nvd.nist.gov/vuln/detail/CVE-2025-21479
How to detect it
This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.
References
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-21479 (government-resource)
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.