dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Jul 2024.
Bifrost Gpu Kernel DriverApplication · Arm

CVE-2024-4610

HIGH · 7.8 CVSS v3.1 Published 2024-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
In the wild 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 allows a local non-privileged user to make improper GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r34p0 through r40p0; Valhall GPU Kernel Driver: from r34p0 through r40p0.

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 and Valhall GPU Kernel Drivers allows local non-privileged users to gain access to already freed memory through improper GPU memory processing operations. The vulnerability affects driver versions r34p0 through r40p0 for both GPU architectures.

MitigationUpdate GPU drivers to versions beyond r40p0 that contain the vendor patch, or apply Arm-supplied security updates to remediate the Use After Free condition in kernel-mode driver memory handling.

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
Bifrost Gpu Kernel DriverApplication
Affected:>= r34p0, < r41p0
Valhall Gpu Kernel DriverApplication
Affected:>= r34p0, < r41p0

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 presence
    Check if Arm Bifrost or Valhall GPU kernel drivers are loaded by running 'lsmod | grep -i arm' or checking /proc/modules for gpu driver modules
    Affected if Arm Bifrost or Valhall GPU kernel modules are loaded on the system
  2. Check Bifrost driver version
    Run 'modinfo <bifrost_driver_module>' or check /sys/module/<bifrost_driver>/version to retrieve the driver version string
    Affected if The reported version is r34p0 or higher but lower than r41p0
  3. Check Valhall driver version
    Run 'modinfo <valhall_driver_module>' or check /sys/module/<valhall_driver>/version to retrieve the driver version string
    Affected if The reported version is r34p0 or higher but lower than r41p0
  4. Verify driver loaded status
    Check if the affected driver modules are currently active using 'lsmod' and confirm they are in use by checking /proc/driver/nvrm_gpu or similar GPU status interfaces depending on the system
    Affected if The vulnerable driver version is loaded and actively handling GPU operations

The system is affected if Arm Bifrost or Valhall GPU kernel drivers with versions r34p0 through r40p0 (less than r41p0) are loaded and actively running.

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 versions beyond r40p0 that contain the vendor patch, or apply Arm-supplied security updates to remediate the Use After Free condition in kernel-mode driver memory handling.

Recommended fix High confidence

r41p0

  1. 1. Identify the current installed version of the Arm Bifrost or Valhall GPU Kernel Driver using system tools or package management
  2. 2. Download the r41p0 or later version of the affected GPU kernel driver from the official Arm developer resources (developer.arm.com)
  3. 3. Install the updated GPU kernel driver package following Arm's standard installation procedures
  4. 4. Reboot the system to ensure the new kernel driver is properly loaded
  5. 5. Verify the installed driver version matches r41p0 or later to confirm the vulnerability is resolved

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

Fix this in Bifrost Gpu Kernel Driver Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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