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

CVE-2025-0050

MEDIUM · 5.9 CVSS v3.1 Published 2025-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges 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 make valid GPU processing operations, including via WebGL or WebGPU, to access a limited amount outside of buffer bounds.This issue affects Bifrost GPU Userspace Driver: from r0p0 through r49p2, from r50p0 through r51p0; Valhall GPU Userspace Driver: from r19p0 through r49p2, from r50p0 through r53p0; Arm 5th Gen GPU Architecture Userspace Driver: from r41p0 through r49p2, from r50p0 through r53p0.

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

Buffer bounds checking flaw in Arm Mali GPU userspace drivers (Bifrost, Valhall, 5th Gen) allows non-privileged processes to read/write limited memory outside allocated buffer boundaries through GPU operations accessible via WebGL or WebGPU.

MitigationUpdate GPU drivers to patched versions (Bifrost: r52p0+, Valhall/5th Gen: r54p0+). Until patched, restrict or disable WebGL/WebGPU in browsers to reduce attack surface.

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, < r49p3>= r50p0, < r54p0
Bifrost Gpu Userspace DriverApplication
Affected:>= r0p0, < r49p3>= r50p0, <= r51p0
Valhall Gpu Userspace DriverApplication
Affected:>= r19p0, < r49p3>= r50p0, < r54p0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 Arm Mali GPU in system
    Check for Mali GPU via lspci, /proc/cpuinfo, or device manager. Look for 'Mali' in GPU identifiers.
    Affected if System does not have an Arm Mali GPU (Bifrost, Valhall, or 5th Gen architecture)
  2. Locate Mali GPU driver version
    Check the Mali driver version file typically at /sys/class/misc/mali0/device/device/driver_version, or use 'cat /sys/class/misc/mali0/device/device/vendor' and search driver release notes for version strings.
    Affected if Unable to locate or determine the installed driver version string
  3. Compare driver version against affected ranges
    Match your found driver version (e.g., r45p0, r52p0) to these ranges: 5th Gen (>= r41p0 and < r49p3, or >= r50p0 and < r54p0), Bifrost (>= r0p0 and < r49p3, or >= r50p0 and <= r51p0), Valhall (>= r19p0 and < r49p3, or >= r50p0 and < r54p0).
    Affected if Installed version falls within any of the affected version ranges listed for your GPU architecture
  4. Verify WebGL or WebGPU accessibility
    Check if WebGL or WebGPU is enabled in browsers or applications. In Chrome/Edge, navigate to chrome://gpu/ to see WebGL/WebGPU status. In Firefox, check about:config for webgl.disabled and webgpu.enabled.
    Affected if WebGL or WebGPU is enabled and accessible to web content or applications on the system

A user is affected if they have an Arm Mali GPU (Bifrost, Valhall, or 5th Gen) with a driver version matching the affected ranges AND WebGL or WebGPU is accessible in their environment.

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 GPU drivers to patched versions (Bifrost: r52p0+, Valhall/5th Gen: r54p0+). Until patched, restrict or disable WebGL/WebGPU in browsers to reduce attack surface.

Recommended fix High confidence

r54p0 for Valhall and 5th Gen; r52p0 or later for Bifrost

  1. 1. Identify which Arm GPU driver(s) are in use: Bifrost, Valhall, or 5th Gen GPU Architecture userspace driver
  2. 2. Check the current installed version of the driver (typically found in /usr/lib/ or via driver package manager)
  3. 3. For Bifrost GPU userspace driver: upgrade to version r52p0 or later
  4. 4. For Valhall GPU userspace driver: upgrade to version r54p0 or later
  5. 5. For 5th Gen GPU Architecture userspace driver: upgrade to version r54p0 or later
  6. 6. Verify the new driver version is loaded after reboot or driver reload
Caveat Driver updates may require kernel module compatibility verification; ensure kernel version supports the new userspace driver

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0050 — 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-0050 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