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

CVE-2024-1065

MEDIUM · 5.9 CVSS v3.1 Published 2024-04-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/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 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 r45p0 through r48p0; Valhall GPU Kernel Driver: from r45p0 through r48p0; Arm 5th Gen GPU Architecture Kernel Driver: from r45p0 through r48p0.

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, and Arm 5th Gen) allows a local non-privileged user to gain access to already freed memory through improper GPU memory processing operations. The issue affects driver versions r45p0 through r48p0.

MitigationUpdate Arm Mali GPU kernel drivers to a version beyond r48p0 (or apply available patches) to address the Use After Free vulnerability. Organizations should identify systems running affected driver versions and prioritize patching given the local privilege escalation potential.

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

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
Low

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

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 hardware in the system
    Run 'lspci | grep -i mali' or check /proc/bus/pci for Mali GPU devices to determine if an Arm Mali GPU is present
    Affected if No Arm Mali GPU is found, the system is not affected by this CVE
  2. Check the Mali GPU kernel driver version
    Use 'modinfo mali' or check the driver version through /sys/module/mali/version (if the module is named differently, check /sys/module/ for mali* entries)
    Affected if The driver version cannot be determined or is not in the r45p0-r48p0 range
  3. Compare driver version against affected range
    Compare the installed driver version to the affected versions: r45p0 <= version < r49p0 for Bifrost, Valhall, and Arm 5th Gen architectures
    Affected if The installed version falls within r45p0 through r48p0 (or any version >= r45p0 and < r49p0), the system is vulnerable
  4. Verify the Mali GPU driver is loaded and active
    Check 'lsmod | grep mali' or look at 'dmesg | grep -i mali' for driver initialization messages to confirm the driver is in use
    Affected if The vulnerable driver version is loaded and the GPU is actively used by the system

A system is affected if it has an Arm Mali GPU (Bifrost, Valhall, or 5th Gen architecture) running a kernel driver version between r45p0 and r48p0 inclusive, with the driver actively loaded.

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 Arm Mali GPU kernel drivers to a version beyond r48p0 (or apply available patches) to address the Use After Free vulnerability. Organizations should identify systems running affected driver versions and prioritize patching given the local privilege escalation potential.

Recommended fix High confidence

r49p0 or later for Bifrost/Valhall/5th Gen GPU Kernel Driver

  1. Identify the affected Arm GPU kernel driver (Bifrost, Valhall, or 5th Gen Architecture) currently installed on the system
  2. Upgrade the Arm Mali GPU kernel driver from the current version (r45p0 through r48p0) to version r49p0 or later
  3. Reboot the system to load the updated driver
  4. Verify the driver version has been updated successfully using system diagnostic tools or by checking the loaded module version
Caveat Standard driver upgrade considerations apply - ensure compatibility with the host kernel version before upgrading

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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