CVE-2025-27038
🔴 High In CISA KEVQualcomm Snapdragon, across 44 enumerated chipsets spanning the Connectivity, Consumer IOT, Industrial IOT, Mobile, Voice & Music and Wearables platforms. The practical target is Android devices on Snapdragon hardware with the Adreno GPU driver, reached from the browser · The record enumerates 44 chipset names rather than version ranges, from AR8031 through to WSA8835, so there is no version to compare against: exposure is a function of the OEM's Android patch level, not of a Qualcomm version string
CVSS (Koffei note)
7.5CVSS (v3.1, CVE List)
7.5EPSS (2026-11-18)
1.044%64.75th percentile
CISA KEV
2025-06-03due 2025-06-24
Exploitation
Yes — CISA KEV since 03/06/2025, the same day the CVE was published (SSVC 06/06/2025: exploitation active, automatable no, technical impact total). Added to this report on 05/11/2026 because it is part of a campaign reported the day before: Sekoia places it as the Class C sandbox escape in an APT29 watering-hole operation, chained behind CVE-2026-3910 for the Chrome renderer, against Android devices running old Chrome on Snapdragon hardware. Dated activity for that chain: a Plerdy compromise from 27/08 to 03/09/2026 and the DarkSword kit uploaded to VirusTotal in September 2026. Same boundary caveat as its partner row: the Plerdy window closed 63 days before this run, so the 60-day recency test rests on the September upload, whose exact day Sekoia does not give
Timeline
- 03/06/2025Added to the CISA KEV catalogue
- 03/06/2025CVE record published (CVE List)
- 24/06/2025CISA deadline for US federal agencies
- 04/11/2026APT29-linked "Poisoned Source" watering-hole campaign hits iOS/Android
- 05/11/2026APT29 "Poisoned Source" campaign hijacks analytics script for mobile exploit delivery
Relationships
exploits suspected named in the same story vendor · Select a box to open its page · All relationships
Risk
7.5 High (v3.1, Qualcomm CNA) — AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, EPSS 1.044% (64.22nd percentile, scored 04/11/2026) — no NVD score and no second scorer (CWE-416 use after free. Qualcomm's entire description is "Memory corruption while rendering graphics using Adreno GPU drivers in Chrome", which is thin for a KEV entry, and the AC:H with UI:R reflects that it is reached through a browser rather than directly)
Fix
Yes, since June 2025 — Qualcomm's June 2025 security bulletin. The fix is not the end of it: Qualcomm patches the driver and each OEM then has to ship it, so a device's real exposure is its Android security patch level rather than anything Qualcomm publishes. No workaround exists
Official description
Memory corruption while rendering graphics using Adreno GPU drivers in Chrome.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
CWE-416