dbcve.org
5th Gen Gpu Architecture Userspace DriverApplication · Arm

CVE-2025-1246

HIGH · 7.8 CVSS v3.1 Published 2025-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Arm Ltd Bifrost GPU Userspace Driver, Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver allows a non-privileged user process to perform valid GPU processing operations, including via WebGL or WebGPU, to access outside of buffer bounds.This issue affects Bifrost GPU Userspace Driver: from r18p0 through r49p3, from r50p0 through r51p0; Valhall GPU Userspace Driver: from r28p0 through r49p3, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Userspace Driver: from r41p0 through r49p3, from r50p0 through r54p0.

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 · high confidence

Improper boundary checking in Arm GPU userspace drivers (Bifrost, Valhall, and 5th Gen) allows a non-privileged user process to access memory outside of allocated buffer bounds when performing GPU operations via WebGL or WebGPU. This is a userspace driver flaw affecting specific version ranges across all three GPU architecture families.

MitigationUpdate Arm GPU userspace drivers to versions beyond r51p0 (Bifrost), r54p0 (Valhall), and r54p0 (5th Gen) to obtain patched boundary validation logic. For embedded/Android devices, apply vendor-specific firmware/driver updates.

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 data
5th Gen Gpu Architecture Userspace DriverApplication
Affected:>= r41p0, < r49p4>= r50p0, < r54p1
Bifrost Gpu Userspace DriverApplication
Affected:>= r48p0, < r49p4= r50p0= r51p0
Valhall Gpu Userspace DriverApplication
Affected:>= r28p0, < r49p4>= r50p0, < r54p1

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GPU architecture family
    Determine if the system uses an Arm Bifrost, Valhall, or 5th Gen GPU by checking system info, lspci output, or device specifications. Arm Mali GPUs (like G710, G610, G510) typically use Bifrost; G710 and later may use Valhall; newer designs may be 5th Gen.
    Affected if The system has an Arm Mali GPU based on Bifrost, Valhall, or 5th Gen architecture families.
  2. Locate installed userspace driver version
    Check for Arm GPU userspace driver packages or libraries. Common locations include /usr/lib/arm-linux-gnueabihf/, /usr/lib/aarch64-linux-gnu/, or vendor-specific paths. Look for files with names like libMali.so, libvulkanArm.so, or similar driver libraries. The driver version is typically embedded in the filename or obtainable via clinfo, vulkaninfo, orEGL_INFO strings.
    Affected if An Arm GPU userspace driver is installed and its version falls within the affected ranges.
  3. Compare driver version against affected ranges
    For Bifrost: versions r48p0 through r49p3, or exactly r50p0 or r51p0 are vulnerable. For Valhall: versions r28p0 through r49p3, or r50p0 through r54p0 are vulnerable. For 5th Gen: versions r41p0 through r49p3, or r50p0 through r54p0 are vulnerable. Match your installed version string (e.g., r49p1) against these ranges.
    Affected if The installed driver version is >= r48p0 and < r49p4 (Bifrost), >= r28p0 and < r49p4 (Valhall), or >= r41p0 and < r49p4 (5th Gen); or is r50p0, r51p0 (Bifrost); or >= r50p0 and < r54p1 (Valhall/5th Gen).
  4. Verify WebGL or WebGPU is accessible
    Check if browsers or applications can access WebGL (via chrome://gpu, about:graphics, or similar) or WebGPU APIs. This vulnerability is triggered specifically when GPU operations are performed through WebGL or WebGPU interfaces. Look for enabled WebGL/WebGPU in browser settings or application configurations.
    Affected if WebGL or WebGPU is enabled and the system uses the affected Arm GPU drivers for rendering.

You are affected if your system has an Arm Bifrost, Valhall, or 5th Gen GPU with a userspace driver version in the affected ranges AND WebGL or WebGPU is enabled for browser or application use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Arm GPU userspace drivers to versions beyond r51p0 (Bifrost), r54p0 (Valhall), and r54p0 (5th Gen) to obtain patched boundary validation logic. For embedded/Android devices, apply vendor-specific firmware/driver updates.

Recommended fix High confidence

Upgrade to r49p4 or r54p1 (depending on current branch) for respective driver families; Bifrost r50p0/r51p0 users should upgrade to r52p0 or later

  1. 1. Identify which Arm GPU userspace driver(s) are in use (5th Gen, Bifrost, or Valhall) by checking the driver package name or firmware version
  2. 2. For 5th Gen GPU Architecture Userspace Driver: upgrade to r49p4 (if currently on r41p0-r49p3) or r54p1 (if currently on r50p0-r54p0)
  3. 3. For Bifrost GPU Userspace Driver: upgrade to r49p4 (if currently on r48p0-r49p3) or r52p0 or later (if currently on r50p0 or r51p0)
  4. 4. For Valhall GPU Userspace Driver: upgrade to r49p4 (if currently on r28p0-r49p3) or r54p1 (if currently on r50p0-r54p0)
  5. 5. Verify the upgrade by checking the driver version matches the target fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 5th Gen Gpu Architecture Userspace Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1246 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1246 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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