Threats / Qualcomm / CVE-2025-21480
CVE-2025-21480
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Qualcomm Multiple Chipsets vulnerability
Multiple Qualcomm chipsets contain an incorrect authorization vulnerability in GPU micronode that allows unauthorized command execution and memory corruption through specific command sequences.
Verdict
Today item — known-exploited.
An attacker can execute unauthorized commands on the GPU micronode by bypassing authorization checks, leading to memory corruption. This vulnerability is actively exploited in the wild and affects multiple Qualcomm chipset variants.
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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.00361 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Qualcomm, Multiple Chipsets. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-863 Incorrect Authorization — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 controls on the micronode.
Business
Attackers gain execution capability on a critical hardware component with minimal detection surface.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute these commands to corrupt memory regions within the GPU or adjacent system memory.
Business
Memory corruption can lead to privilege escalation, data exfiltration, or persistent code execution.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the memory corruption to escape the GPU sandbox or gain kernel-level access.
Business
Complete device compromise becomes possible, affecting confidentiality and integrity of all 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