dbcve.org
5th Gen Gpu Architecture FirmwareOperating system · Arm

CVE-2024-0153

HIGH · 7.8 CVSS v3.1 Published 2024-07-01
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
Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Arm Ltd Valhall GPU Firmware, Arm Ltd Arm 5th Gen GPU Architecture Firmware allows a local non-privileged user to make improper GPU processing operations to access a limited amount outside of buffer bounds. If the operations are carefully prepared, then this in turn could give them access to all system memory. This issue affects Valhall GPU Firmware: from r29p0 through r46p0; Arm 5th Gen GPU Architecture Firmware: from r41p0 through r46p0.

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

Buffer overflow vulnerability in Arm Valhall and 5th Gen GPU firmware allows local non-privileged users to perform improper GPU processing operations that access memory outside buffer boundaries. With careful preparation, this limited out-of-bounds access can be escalated to read/write across all system memory.

MitigationUpdate GPU firmware to r47p0 or later. Contact device manufacturers for firmware updates as this affects downstream products using these GPU architectures.

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 FirmwareOperating system
Affected:>= r41p0, < r47p0
Valhall Gpu FirmwareOperating system
Affected:>= r29p0, < r47p0

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 the GPU hardware in the system
    Use system inventory commands such as lspci, lsdev, or vendor-specific tools to enumerate the installed GPU. Look for Arm Mali GPUs based on Valhall architecture or 5th Gen architecture.
    Affected if The system contains an Arm Valhall or 5th Gen Mali GPU
  2. Determine the installed GPU firmware version
    Query the GPU firmware version through system interfaces such as /sys/class/drm entries, dmesg logs, vendor management tools, or firmware files in /lib/firmware. The exact method depends on the operating system and GPU driver in use.
    Affected if The firmware version cannot be determined or the system does not have Arm GPU firmware
  3. Compare the firmware version against the affected ranges
    Check if the installed version falls within: Arm 5th Gen Gpu Architecture Firmware >= r41p0 and < r47p0, OR Arm Valhall Gpu Firmware >= r29p0 and < r47p0
    Affected if The installed version is r41p0 through r46p9 for 5th Gen architecture, or r29p0 through r46p9 for Valhall architecture

The system is affected if it contains an Arm Valhall or 5th Gen Mali GPU with firmware version r41p0-r46p9 (5th Gen) or r29p0-r46p9 (Valhall).

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 firmware to r47p0 or later. Contact device manufacturers for firmware updates as this affects downstream products using these GPU architectures.

Recommended fix High confidence

r47p0 or later

  1. Identify the specific Arm GPU product and current firmware version (r41p0 through r46p0 for 5th Gen, or r29p0 through r46p0 for Valhall)
  2. Obtain the fixed firmware version r47p0 or later from Arm's official firmware distribution channels (developer.arm.com or your device OEM)
  3. Apply the firmware update following the standard procedure for your specific GPU product/board - this typically involves flashing the new firmware binary to the GPU device
  4. Reboot the GPU and verify the firmware has been updated to r47p0 or later by checking the firmware version string
Caveat Firmware updates carry inherent risk; ensure backup and rollback procedures are in place before applying

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

Fix this in 5th Gen Gpu Architecture Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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