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

CVE-2024-1395

MEDIUM · 6.7 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 →
72/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 Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user to make improper GPU memory processing operations. If the system’s memory is carefully prepared by the user, then this in turn could give them access to already freed memory. This issue affects 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 5th Gen GPU Architecture Kernel Driver (r41p0-r47p0) allows local non-privileged users to access freed GPU memory through improper memory processing operations. The vulnerability exists in kernel-mode driver code that fails to properly manage memory lifecycle, potentially leading to arbitrary memory reads/writes.

MitigationUpdate Arm Mali GPU kernel driver to version r48p0 or later which contains the fix. Apply vendor-supplied patches or obtain updated driver binaries from Arm's official distribution channels.

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

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
None

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

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 presence
    Check for Mali GPU device files (e.g., /dev/mali0, /dev/mem) or loaded Mali kernel modules using 'lsmod | grep mali' or 'ls -la /dev/mali*'
    Affected if No Mali GPU device or driver module is found on the system - the vulnerability only applies to systems with Arm 5th Gen GPUs
  2. Locate the Mali kernel driver version
    Query the driver version through sysfs (e.g., cat /sys/class/misc/mali0/device/driver/version) or use 'modinfo mali' if the module is loaded, or check /proc driver/mali/version
    Affected if Unable to determine the driver version - cannot assess exposure without version confirmation
  3. Compare installed version against affected range
    Compare the obtained version string (e.g., r45p0, r47p0) to the affected range: version >= r41p0 AND < r48p0 indicates vulnerability
    Affected if Version is r41p0, r42p0, r43p0, r44p0, r45p0, r46p0, or r47p0 - these versions contain the Use After Free flaw
  4. Verify driver is actively loaded
    Confirm the Mali driver is currently loaded and operational using 'lsmod | grep -i mali' or by checking /proc/modules for mali entries
    Affected if Driver is loaded and running - the Use After Free can only be exploited when the vulnerable driver code is active in memory

System is affected if it has an Arm 5th Gen Mali GPU with the kernel driver loaded and the driver version is between r41p0 and r47p0 inclusive.

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 driver to version r48p0 or later which contains the fix. Apply vendor-supplied patches or obtain updated driver binaries from Arm's official distribution channels.

Recommended fix High confidence

r48p0

  1. Identify the current version of the Arm 5th Gen GPU Architecture Kernel Driver installed on the system
  2. If the version is between r41p0 and r47p0 (inclusive), the system is vulnerable
  3. Upgrade the GPU driver to version r48p0 or later
  4. Verify the upgrade was successful by checking the driver version after installation
  5. Reboot the system if required by the driver update process

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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