Skip to content
vulnerability

CVE-2025-21480

8.6
High
KEV · Exploited in wildEPSS 0.43%Patch available

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

exploited
Yes, in CISA KEV since 3 Jun 2025fix by 24 Jun 2025 (CISA deadline for US federal agencies)
fix
Patch available see the advisory in the references
likelihood
EPSS 0.43%
Published 3 Jun 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: noAV · localCWE-863· Incorrect Authorization

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch · per-resource ACL

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requirednoneuser interactionrequiredscopechangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
common questions

Is CVE-2025-21480 being exploited?

Yes. CVE-2025-21480 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-21480?

CVE-2025-21480 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-21480?

Yes. A fix has been recorded for CVE-2025-21480. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-21480 affect?

CVE-2025-21480 affects qualcomm:aqt1000_firmware, qualcomm:fastconnect_6200_firmware, qualcomm:fastconnect_6700_firmware, qualcomm:fastconnect_6800_firmware, and 26 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
qualcomm:aqt1000_firmwarequalcomm:fastconnect_6200_firmwarequalcomm:fastconnect_6700_firmwarequalcomm:fastconnect_6800_firmwarequalcomm:fastconnect_6900_firmwarequalcomm:fastconnect_7800_firmwarequalcomm:qca6391_firmwarequalcomm:qcm4490_firmwarequalcomm:qcs4490_firmwarequalcomm:sc8380xp_firmwarequalcomm:sd855_firmwarequalcomm:sm4635_firmwarequalcomm:sm6250_firmwarequalcomm:sm6650_firmwarequalcomm:sm6650p_firmwarequalcomm:sm7325p_firmwarequalcomm:sm7635_firmwarequalcomm:sm7675_firmwarequalcomm:sm7675p_firmwarequalcomm:sm8550p_firmwarequalcomm:sm8635_firmwarequalcomm:sm8635p_firmwarequalcomm:sm8650q_firmwarequalcomm:snapdragon_4_gen_1_mobile_platform_firmwarequalcomm:snapdragon_460_mobile_platform_firmwarequalcomm:snapdragon_480_5g_mobile_platform_firmwarequalcomm:snapdragon_480\+_5g_mobile_platform_\(sm4350-ac\)_firmwarequalcomm:snapdragon_662_mobile_platform_firmwarequalcomm:snapdragon_680_4g_mobile_platform_firmwarequalcomm:snapdragon_685_4g_mobile_platform_\(sm6225-ad\)_firmware
affected versions
Qualcomm, Inc. Snapdragon
  • affectedAQT1000
  • affectedFastConnect 6200
  • affectedFastConnect 6700
  • affectedFastConnect 6800
  • affectedFastConnect 6900
  • affectedFastConnect 7800
  • affectedQCA6391
  • affectedQCM4490
  • affectedQCS4490
  • affectedSC8380XP
  • affectedSD855
  • affectedSM4635
  • affectedSM6250
  • affectedSM6650
  • affectedSM6650P
  • affectedSM7325P
  • affectedSM7635
  • affectedSM7675
  • affectedSM7675P
  • affectedSM8550P
  • affectedSM8635
  • affectedSM8635P
  • affectedSM8650Q
  • affectedSnapdragon 4 Gen 1 Mobile Platform
  • affectedSnapdragon 460 Mobile Platform
  • affectedSnapdragon 480 5G Mobile Platform
  • affectedSnapdragon 480+ 5G Mobile Platform (SM4350-AC)
  • affectedSnapdragon 662 Mobile Platform
  • affectedSnapdragon 680 4G Mobile Platform
  • affectedSnapdragon 685 4G Mobile Platform (SM6225-AD)
  • affectedSnapdragon 690 5G Mobile Platform
  • affectedSnapdragon 695 5G Mobile Platform
  • affectedSnapdragon 720G Mobile Platform
  • affectedSnapdragon 778G 5G Mobile Platform
  • affectedSnapdragon 778G+ 5G Mobile Platform (SM7325-AE)
  • affectedSnapdragon 782G Mobile Platform (SM7325-AF)
  • affectedSnapdragon 7c+ Gen 3 Compute
  • affectedSnapdragon 8 Gen 2 Mobile Platform
  • affectedSnapdragon 8 Gen 3 Mobile Platform
  • affectedSnapdragon 8+ Gen 2 Mobile Platform
  • affectedSnapdragon 855 Mobile Platform
  • affectedSnapdragon 855+/860 Mobile Platform (SM8150-AC)
  • affectedSnapdragon 865 5G Mobile Platform
  • affectedSnapdragon 865+ 5G Mobile Platform (SM8250-AB)
  • affectedSnapdragon 870 5G Mobile Platform (SM8250-AC)
  • affectedSnapdragon 888 5G Mobile Platform
  • affectedSnapdragon 888+ 5G Mobile Platform (SM8350-AC)
  • affectedSnapdragon AR1 Gen 1 Platform
  • affectedSnapdragon AR1 Gen 1 Platform "Luna1"
  • affectedSnapdragon X55 5G Modem-RF System
  • affectedSXR2230P
  • affectedSXR2250P
  • affectedSXR2330P
  • affectedWCD9341
  • affectedWCD9370
  • affectedWCD9375
  • affectedWCD9378
  • affectedWCD9380
  • affectedWCD9385
  • affectedWCD9390
  • affectedWCD9395
  • affectedWCN3950
  • affectedWCN3988
  • affectedWCN6450
  • affectedWCN6650
  • affectedWCN6755
  • affectedWCN7861
  • affectedWCN7881
  • affectedWSA8810
  • affectedWSA8815
  • affectedWSA8830
  • affectedWSA8832
  • affectedWSA8835
  • affectedWSA8840
  • affectedWSA8845
  • affectedWSA8845H

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 6 Jun 2025 (SSVC 2.0.3).

timeline

  1. 3 Jun 2025Added to CISA KEV (exploited in the wild)
  2. 3 Jun 2025Published · same day later
  3. 6 Jun 2025CISA SSVC assessment: exploitation active · 3 days later
  4. 24 Jun 2025CISA remediation due date (US federal agencies) · 18 days later
  5. 26 Feb 2026CVE record last updated · 248 days (about 8 months) later
  6. 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
2 references in the CVE record: 2 links
  • Linkdocs.qualcomm.com /product/publicresources/securitybulletin/june-2025-bulletin.html
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-21480

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved