IRONSMITHINTEL
HIGHCVSS8.6
|
Actively Exploited
|CISA KEV|CVE-2025-21479|Auth: none — unauthenticated|Reboot: required|Manual only

Qualcomm Multiple Chipsets Incorrect Authorization Vulnerability (CVE-2025-21479)

Multiple Qualcomm chipsets contain an incorrect authorization vulnerability. This vulnerability allows for memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.

Published Jun 3, 2025 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2025-06-24 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Incorrect Authorization (CWE-863) vulnerability in Qualcomm Multiple Chipsets. Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands. Exploitation requires local access, low attack complexity, no authentication required, and user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

IT Security
Running aqt1000 firmware: -; fastconnect 6200 firmware: -; fastconnect 6700 firmware: -; fastconnect 6900 firmware: -; fastconnect 7800 firmware: -; fastconnect 6800 firmware: -; qca6391 firmware: -; qcm4490 firmware: -; qcs4490 firmware: -; sd855 firmware: -; sm4635 firmware: -; sm6250 firmware: -; sm6650 firmware: -; sm6650p firmware: -; sm7325p firmware: -; sm7635 firmware: -; sm7675 firmware: -; sm7675p firmware: -; sm8550p firmware: -; sm8635 firmware: -; sm8635p firmware: -; sm8650q firmware: -; snapdragon 4 gen 1 mobile platform firmware: -; snapdragon 460 mobile platform firmware: -; snapdragon 480 5g mobile platform firmware: -; snapdragon 480\+ 5g mobile platform \(sm4350-ac\) firmware: -; snapdragon 662 mobile platform firmware: -; snapdragon 680 4g mobile platform firmware: -; snapdragon 685 4g mobile platform \(sm6225-ad\) firmware: -; snapdragon 690 5g mobile platform firmware: -; snapdragon 695 5g mobile platform firmware: -; snapdragon 720g mobile platform firmware: -; snapdragon 778g 5g mobile platform firmware: -; snapdragon 778g\+ 5g mobile platform \(sm7325-ae\) firmware: -; snapdragon 782g mobile platform \(sm7325-af\) firmware: -; snapdragon 7c\+ gen 3 compute firmware: -; snapdragon 8 gen 2 mobile platform firmware: -; snapdragon 8 gen 3 mobile platform firmware: -; snapdragon 8\+ gen 2 mobile platform firmware: -; snapdragon 855 mobile platform firmware: -; snapdragon 855\+\/860 mobile platform \(sm8150-ac\) firmware: -; snapdragon 865 5g mobile platform firmware: -; snapdragon 865\+ 5g mobile platform \(sm8250-ab\) firmware: -; snapdragon 870 5g mobile platform \(sm8250-ac\) firmware: -; snapdragon 888 5g mobile platform firmware: -; snapdragon 888\+ 5g mobile platform \(sm8350-ac\) firmware: -; snapdragon ar1 gen 1 firmware: -; snapdragon ar1 gen 1 platform \"luna1\" firmware: -; snapdragon x55 5g modem-rf system firmware: -; sxr2230p firmware: -; sxr2250p firmware: -; sxr2330p firmware: -; wcd9395 firmware: -; wcn3950 firmware: -; wcn3988 firmware: -; wcn6450 firmware: -; wcn6650 firmware: -; wcn6755 firmware: -; wcn7861 firmware: -; wcn7881 firmware: -; wsa8810 firmware: -; wsa8815 firmware: -; wsa8830 firmware: -; wsa8835 firmware: -; wsa8840 firmware: -; wsa8845 firmware: -; wsa8845h firmware: -; wcd9341 firmware: -; wcd9370 firmware: -; wcd9375 firmware: -; wcd9378 firmware: -; wcd9380 firmware: -; wcd9385 firmware: -; wcd9390 firmware: -; wsa8832 firmware: -
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2025-06-03 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2025-06-24.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2025-21479's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.