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

CVE-2024-1067

HIGH · 7.4 CVSS v3.1 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
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 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. On Armv8.0 cores, there are certain combinations of the Linux Kernel and Mali GPU kernel driver configurations that would allow the GPU operations to affect the userspace memory of other processes. This issue affects Bifrost GPU Kernel Driver: from r41p0 through r47p0; Valhall GPU Kernel Driver: from r41p0 through r47p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r47p0.

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 Mali GPU kernel drivers (Bifrost, Valhall, 5th Gen) allows local non-privileged users to make improper GPU memory processing operations. On Armv8.0 cores, specific Linux Kernel and Mali GPU driver configurations permit GPU operations to affect userspace memory of other processes, enabling potential cross-process memory corruption.

MitigationUpdate Mali GPU kernel drivers to a version beyond r47p0. Review and apply any Linux Kernel patches addressing Armv8.0 core GPU memory isolation configurations.

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

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

CVSS:3.1/AV:L/AC:H/PR:N/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. Detect Mali GPU kernel driver presence
    Check for loaded Mali GPU kernel modules by running 'lsmod | grep -i mali' or examining /proc/modules for mali_kbase, mali, or similar Mali driver modules
    Affected if A Mali GPU kernel driver module is loaded in memory
  2. Identify the exact driver version
    Run 'modinfo <mali_driver_module_name>' and locate the 'version' or ' vermagic' field to determine the driver release (e.g., r41p0, r45p0, r47p0)
    Affected if The driver version falls within r41p0 to r47p0 (inclusive of r41p0, exclusive of r48p0)
  3. Confirm CPU architecture is Armv8.0
    Check /proc/cpuinfo for 'CPU architecture: 8' or 'aarch64' and verify the processor is an Armv8.0 core variant
    Affected if The system runs on Armv8.0 cores and uses the affected Mali GPU driver version
  4. Verify GPU memory processing is exposed
    Confirm that the Mali GPU device (/dev/mali0 or /dev/dri/card*) is accessible and that userspace applications can submit GPU work (check /sys/class/drm or /dev for GPU device nodes)
    Affected if GPU device nodes exist and the vulnerable driver version is in use on Armv8.0 hardware

If a Mali GPU kernel driver module is loaded and its version is r41p0 or higher but lower than r48p0, running on Armv8.0 hardware, the environment is affected by this Use After Free vulnerability.

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 Mali GPU kernel drivers to a version beyond r47p0. Review and apply any Linux Kernel patches addressing Armv8.0 core GPU memory isolation configurations.

Recommended fix High confidence

Mali GPU Kernel Driver r48p0 or later

  1. 1. Identify the current version of the Arm Mali GPU kernel driver installed on the system by checking /sys/module/mali_kbase/version or reviewing kernel module information
  2. 2. Obtain the updated Mali GPU kernel driver version r48p0 or later from Arm's official developer resources at developer.arm.com
  3. 3. Update the Linux kernel or rebuild the Mali GPU kernel driver module with the fixed version (r48p0 or newer)
  4. 4. Reboot the system to load the corrected kernel driver
  5. 5. Verify the driver version has been updated to r48p0 or later to confirm the vulnerability is patched

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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