Threats / Qualcomm / CVE-2025-21479
CVE-2025-21479
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Qualcomm Multiple Chipsets vulnerability
Multiple Qualcomm chipsets contain an incorrect authorization vulnerability allowing unauthorized GPU micronode command execution, leading to memory corruption.
Verdict
Today item — known-exploited.
An authorization flaw in Qualcomm chipsets permits attackers to execute unauthorized commands on the GPU micronode, causing memory corruption. Active exploitation in the wild indicates immediate risk to affected devices.
CISA KEV Yes · 2025-06-035EPSS 0.00778 (verify live)6Exploit Public PoC7CVSS 8.63CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-03).
Probability (EPSS)
EPSS 0.00778 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.6 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) · Affected: Qualcomm, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-863 Incorrect Authorization — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a specific sequence of GPU commands that bypass authorization checks on the micronode.
Business
Device security perimeter is compromised through GPU-level access without proper privilege validation.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute these unauthorized commands to corrupt GPU memory regions and adjacent system memory.
Business
Memory integrity is violated, enabling potential code execution or denial of service across GPU and host systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the memory corruption to escalate privileges or break out of GPU isolation boundaries.
Business
Containment of GPU workloads fails, allowing lateral movement to sensitive system components or user data.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05