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

CVE-2025-6349

MEDIUM · 5.1 CVSS v3.1 Published 2025-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/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
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU memory processing operations to gain access to already freed memory.This issue affects Valhall GPU Kernel Driver: from r53p0 through r54p1; Arm 5th Gen GPU Architecture Kernel Driver: from r53p0 through r54p1.

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 confidence

Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver and Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to gain access to already freed memory through improper GPU memory processing operations. This affects versions r53p0 through r54p1 of both drivers.

MitigationApply vendor-provided patches to update the GPU kernel drivers beyond r54p1 once available; until then, restrict local unprivileged access to systems with affected GPU drivers as a compensating control.

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:>= r53p0, < r54p2
Valhall Gpu Kernel DriverApplication
Affected:>= r53p0, < r54p2

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
None

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

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 hardware present
    Check system hardware details (lspci, /proc/bus/pci, or vendor-specific tools) for Arm GPU devices. Look for Valhall or Arm 5th Gen GPU entries in the PCI or hardware inventory.
    Affected if System contains Arm Valhall or Arm 5th Gen GPU hardware
  2. Locate Arm GPU kernel driver
    Check loaded kernel modules (lsmod) or /dev/ directory for Arm GPU driver files (typically named with 'mali' or 'arm' GPU driver conventions). Use 'modprobe -l' or check /lib/modules/$(uname -r)/kernel/drivers/gpu/ for arm subdirectory.
    Affected if Arm GPU kernel driver module is loaded or present on the system
  3. Query driver version
    Use 'modinfo <driver_module_name>' to retrieve the driver version, or check dmesg output for GPU driver initialization messages showing version string. The version typically appears as rXXpY format.
    Affected if Driver version is r53p0 through r54p1 (inclusive)
  4. Verify driver version range
    Compare the installed driver version string against the affected range: r53p0, r53p1, r54p0, r54p1 are vulnerable. Versions below r53p0 or r54p2 and above are not affected.
    Affected if Installed version falls within >= r53p0 and < r54p2

User is affected if Arm Valhall or Arm 5th Gen GPU kernel driver versions r53p0 through r54p1 are in use on the system.

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-provided patches to update the GPU kernel drivers beyond r54p1 once available; until then, restrict local unprivileged access to systems with affected GPU drivers as a compensating control.

Recommended fix High confidence

r54p2

  1. Identify the currently installed Arm GPU kernel driver version using modinfo or package management tools
  2. Upgrade the Arm 5th Gen GPU Architecture Kernel Driver and/or Valhall GPU Kernel Driver to version r54p2 or later
  3. Reboot the system or reload the kernel module to ensure the new driver is loaded
  4. Verify the installed driver version matches r54p2 or newer using modinfo or equivalent tool

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-6349 — 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-6349 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