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

CVE-2024-4607

HIGH · 7.8 CVSS v3.1 Published 2024-08-05
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 to make improper GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r41p0 through r49p0; Valhall GPU Kernel Driver: from r41p0 through r49p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p0.

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

A Use After Free vulnerability exists in Arm's Bifrost, Valhall, and 5th Gen GPU kernel drivers (versions r41p0 through r49p0). A local non-privileged user can exploit improper GPU memory processing operations to access memory that has already been freed, potentially leading to privilege escalation or system instability.

MitigationUpdate the affected GPU kernel drivers to version r50p0 or later to obtain the patched driver. For systems where immediate patching is not feasible, consider restricting local user access to GPU resources or implementing monitoring for suspicious memory access patterns.

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

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 Mali GPU kernel driver presence
    Check for Mali GPU device nodes in /dev (such as /dev/mali0) or list loaded kernel modules using 'lsmod | grep -i mali' and look for modules named mali, bifrost, valhall, or arm-mali
    Affected if No Arm Mali GPU drivers are present on the system, the system is not affected by this CVE
  2. Determine the installed driver version
    Use 'cat /sys/class/misc/mali0/device/version' or check /proc driver/mali version file. Alternatively, run 'modinfo <driver_module_name>' and look for the version field in the output
    Affected if Unable to retrieve a version number from the driver, manual verification may be required
  3. Compare driver version against affected range
    Verify if the installed version falls within r41p0 through r49p0. Versions r41p0 <= version < r50p0 are affected. Versions r50p0 and later are patched
    Affected if The installed driver version is r41p0 or higher but lower than r50p0, indicating the system is vulnerable
  4. Check if non-privileged user GPU access is permitted
    Examine permissions on GPU device nodes (ls -la /dev/mali* /dev/dri/*) and verify whether users in the 'video' or 'render' group exist. Run 'getent group video' and 'getent group render' to check group membership
    Affected if Non-privileged users have access to GPU device nodes (world-readable/writable or belong to accessible groups), making exploitation possible

A system is affected if it runs any Arm Mali Bifrost, Valhall, or 5th Gen GPU kernel driver with version r41p0 through r49p0 and permits local non-privileged user access to the GPU resources.

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 the affected GPU kernel drivers to version r50p0 or later to obtain the patched driver. For systems where immediate patching is not feasible, consider restricting local user access to GPU resources or implementing monitoring for suspicious memory access patterns.

Recommended fix High confidence

r50p0 or later version of the affected Arm GPU kernel driver (Bifrost, Valhall, or 5th Gen GPU Architecture)

  1. Identify which Arm GPU kernel driver is in use (Bifrost, Valhall, or 5th Gen GPU Architecture)
  2. Check the current driver version to confirm it is within the affected range (r41p0 through r49p0)
  3. Obtain and install the fixed driver version r50p0 or later from Arm's official driver distribution channels
  4. Reboot the system or reload the kernel driver module to apply the updated driver
  5. Verify the installed driver version is r50p0 or higher to confirm the remediation

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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