Threats / Qualcomm / CVE-2025-27038
CVE-2025-27038
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Qualcomm Multiple Chipsets vulnerability
Use-after-free vulnerability in Qualcomm Adreno GPU drivers affecting multiple chipsets. Allows memory corruption during graphics rendering in Chrome. Actively exploited in the wild.
Verdict
Today item — known-exploited.
A use-after-free flaw in Qualcomm's Adreno GPU drivers enables memory corruption through malicious graphics rendering. The vulnerability is being actively exploited. Patch Qualcomm chipset firmware and update Chrome immediately.
CISA KEV Yes · 2025-06-035EPSS 0.01016 (verify live)6CVSS 7.53CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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.01016 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 7.5 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/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-416 Use After Free — weakness family: Memory safety.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
Craft a malicious webpage or graphics content that triggers improper memory handling in the Adreno GPU driver during rendering.
Business
User systems running affected Qualcomm chipsets become vulnerable to code execution and data compromise through browser-based attack vectors.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Exploit the use-after-free condition to corrupt memory and achieve arbitrary code execution with GPU driver privileges.
Business
Attackers gain elevated access to device resources, enabling persistent compromise, credential theft, and lateral movement within enterprise networks.
3
Lateral reach — past segmentation narrative 3
Attacker
Establish persistence or exfiltrate sensitive data from compromised devices at scale.
Business
Organizations face data breaches, operational disruption, and reputational damage from widespread device compromise across mobile and embedded systems.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by qualcommCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.