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

CVE-2025-0819

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
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r44p0 through r49p3, from r50p0 through r51p0; Valhall GPU Kernel Driver: from r44p0 through r49p3, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Kernel Driver: from r44p0 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

Use After Free vulnerability in Arm Ltd Bifrost, Valhall, and Arm 5th Gen GPU Kernel Drivers allows a local non-privileged user process to perform GPU memory processing operations to gain access to already freed memory, potentially leading to privilege escalation or information disclosure.

MitigationApply vendor-supplied driver updates to address the affected version ranges (r44p0-r49p3, r50p0-r51p0 for Bifrost; r44p0-r49p3, r50p0-r54p0 for Valhall and Arm 5th Gen). Consider restricting access to GPU operations until patches are applied.

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 Kernel DriverApplication
Affected:>= r44p0, < r49p4>= r50p0, < r54p1
Bifrost Gpu Kernel DriverApplication
Affected:>= r44p0, < r49p4= r50p0= r51p0
Valhall Gpu Kernel DriverApplication
Affected:>= r44p0, < 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 Arm GPU driver in use
    Check loaded kernel modules for mali_kbase, mali, or arm/malidrivers. Run 'lsmod | grep -i mali' or check /proc/modules. Also examine /sys/class/drm/ for card* devices and their driver info via 'cat /sys/class/drm/card0/device/driver'
    Affected if The system uses Bifrost, Valhall, or Arm 5th Gen Mali GPU kernel drivers (mali_kbase module)
  2. Determine driver version
    Run 'modinfo mali_kbase 2>/dev/null | grep version' or 'cat /sys/module/mali_kbase/parameters/version' if available. On Android, check /vendor/lib/modules/ or /system/lib/modules/ for the driver file and run 'strings' on it to find version strings like 'r44p0', 'r50p0', etc.
    Affected if Driver version cannot be determined or shows a version starting with r44p0 or higher
  3. Compare against affected version ranges
    If a version is obtained, compare it to: Bifrost: r44p0 to r49p3, r50p0, r51p0; Valhall and Arm 5th Gen: r44p0 to r49p3, r50p0 to r54p0. Note that r49p4 and r54p1 are the fixed versions
    Affected if Installed version falls within r44p0 to r49p3, r50p0 to r51p0 (Bifrost), or r44p0 to r49p3, r50p0 to r54p0 (Valhall/5th Gen)
  4. Verify non-privileged GPU process access
    Check if unprivileged users can access GPU operations. Examine /dev/mali0 or /dev/dri/card* permissions with 'ls -la /dev/mali* /dev/dri/card*'. Verify group membership and device ACLs allow non-root GPU access
    Affected if Non-privileged users have direct access to GPU device nodes without restriction

The system is affected if it runs Arm Mali GPU kernel drivers (Bifrost, Valhall, or 5th Gen) with version numbers between r44p0 and the fixed releases (r49p4 for older branches, r54p1 for newer branches), and non-privileged users can access GPU operations.

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

Apply vendor-supplied driver updates to address the affected version ranges (r44p0-r49p3, r50p0-r51p0 for Bifrost; r44p0-r49p3, r50p0-r54p0 for Valhall and Arm 5th Gen). Consider restricting access to GPU operations until patches are applied.

Recommended fix High confidence

r49p4 or r54p1 (depending on the GPU architecture - Bifrost can also use r52p0+)

  1. 1. Identify the current installed version of the Arm GPU kernel driver (bifrost, valhall, or arm-5th-gen) using: cat /sys/class/drm/*/device/uevent or modinfo <driver_name>
  2. 2. Determine which GPU architecture your system uses (5th Gen, Bifrost, or Valhall) from the driver in use
  3. 3. For Bifrost GPU: upgrade to version r49p4 or later (or r52p0 or later to avoid r50p0/r51p0)
  4. 4. For Valhall GPU: upgrade to version r54p1 or later
  5. 5. For 5th Gen GPU Architecture: upgrade to version r54p1 or later
  6. 6. Verify the upgrade was successful by checking the driver version again after reboot or module reload
Caveat Newer driver releases may have API changes; test in non-production environment first if possible

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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