CVE-2025-27038
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMemory corruption while rendering graphics using Adreno GPU drivers in Chrome.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMemory corruption vulnerability in Chrome's GPU rendering pipeline when using Adreno GPU drivers, potentially allowing arbitrary code execution or denial of service via specially crafted graphics content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Chrome hardware acceleration is enabledNavigate to chrome://settings in Chrome, click 'Advanced', and under 'System' check if 'Use hardware acceleration when available' is turned ON. Alternatively, visit chrome://gpu to see GPU information.Affected if Hardware acceleration is enabled - this is required for the vulnerable GPU driver code path to be exercised
-
Identify the GPU hardware in useOpen chrome://gpu and look for information under 'Graphics Feature Status'. Check if 'WebGL' and 'Hardware Acceleration' show as enabled. Note the GPU vendor name (look for Qualcomm/Adreno).Affected if The system uses a Qualcomm Adreno GPU, as this vulnerability specifically targets Adreno GPU driver code paths
-
Check for affected Qualcomm firmware componentsOn Windows, open Device Manager, expand 'Display adapters', and note the GPU model. On Android, check under Settings > About Phone > Baseband or use terminal commands like 'dmesg | grep -i qcom' or 'cat /sys/class/devcoredump/ device/uevent' to identify Qualcomm components. On Linux, check 'lspci | grep -i vga' or 'lshw -C display'.Affected if The system contains any of these Qualcomm firmware components: Ar8031, Csra6620, Csra6640, Fastconnect 7800, Qca2066, Qca6391, Qcm6125, or Qcm8550
-
Verify Chrome version as secondary indicatorIn Chrome, navigate to chrome://settings/help to see the current version number. Compare against any Chrome security advisories for this CVE.Affected if Chrome version is older than the patched version that addresses this specific vulnerability
The user is affected if Chrome hardware acceleration is enabled AND the system contains a Qualcomm Adreno GPU with any of the listed firmware components (Ar8031, Csra6620, Csra6640, Fastconnect 7800, Qca2066, Qca6391, Qcm6125, or Qcm8550).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Chrome to the latest version containing the security fix; as a temporary workaround, disable hardware acceleration in Chrome settings to prevent exploitation through the vulnerable GPU driver code path.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27038 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data