CVE-2024-0671
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 · uneditedUse After Free vulnerability in Arm Ltd Midgard GPU Kernel Driver, 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 Midgard GPU Kernel Driver: from r19p0 through r32p0; Bifrost GPU Kernel Driver: from r7p0 through r48p0; Valhall GPU Kernel Driver: from r19p0 through r48p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 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 confidenceA Use After Free vulnerability in Arm Ltd's GPU kernel drivers (Midgard, Bifrost, Valhall, and Arm 5th Gen architectures) allows a local non-privileged user to make improper GPU memory processing operations that gain access to already freed memory. This affects specific version ranges across all four GPU driver families.
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>= r41p0, < r49p0>= r7p0, < r49p0>= r19p0, <= r32p0>= r19p0, < r49p0CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Arm GPU hardware presentCheck system hardware info (lspci, /proc/bus/pci, or device tree) for Arm Mali GPU components (e.g., Mali-G71, Mali-G76, Mali-G77, Mali-G710, etc.)Affected if System contains Arm Mali GPU hardware that uses one of the affected driver families
-
Identify which GPU kernel driver family is loadedList loaded kernel modules (lsmod) or check /proc/modules for Arm GPU drivers such as mali_kbase, panfrost, or similar Mali driver modulesAffected if An Arm GPU kernel driver module is loaded (Midgard, Bifrost, Valhall, or 5th Gen architecture driver)
-
Retrieve the installed driver versionUse modinfo on the loaded Mali driver module (e.g., modinfo mali_kbase) to read the version parameter, or check /sys/module/<drivername>/versionAffected if Cannot determine driver version - version info is missing or inaccessible
-
Compare against affected version rangesCross-reference the obtained version with these ranges: Bifrost: >= r7p0 and < r49p0, Valhall: >= r19p0 and < r49p0, Midgard: >= r19p0 and <= r32p0, 5th Gen: >= r41p0 and < r49p0Affected if Installed version falls within any of these ranges and the driver family matches the version range criteria
-
Check for local user accessReview system user accounts and group membership to determine if non-privileged local users exist or can access the systemAffected if Local non-privileged users have access to the system with affected GPU drivers (exploitation requires local user, not remote)
-
Review kernel memory access logsInspect kernel logs (dmesg, journalctl) and kernel memory debugging interfaces (e.g., kmemleak, kasan if enabled) for signs of use-after-free or memory corruption related to GPU operationsAffected if Logs show memory allocation/free mismatches or suspicious memory access patterns in GPU driver code
System is affected if it runs Arm Mali GPU hardware with a kernel driver version matching any of the four affected version ranges (Bifrost r7p0 to r49p0, Valhall r19p0 to r49p0, Midgard r19p0 to r32p0, or 5th Gen r41p0 to r49p0) and permits local non-privileged user access.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply patches or updated GPU drivers provided by Arm Ltd for the affected version ranges. Until patches are applied, restrict local user access to systems with affected GPU hardware and monitor for suspicious memory access patterns.
r49p0 or later for Bifrost, Valhall, and 5th Gen architectures; release newer than r32p0 for Midgard
- 1. Identify the specific Arm GPU architecture in use (Midgard, Bifrost, Valhall, or 5th Gen) by checking the hardware or system documentation.
- 2. For Midgard GPU Kernel Driver: upgrade to a release newer than r32p0 (contact Arm for specific stable release).
- 3. For Bifrost GPU Kernel Driver: upgrade to r49p0 or later.
- 4. For Valhall GPU Kernel Driver: upgrade to r49p0 or later.
- 5. For Arm 5th Gen GPU Architecture Kernel Driver: upgrade to r49p0 or later.
- 6. Verify the new driver version by checking /sys/class/drm/*/device/version or using vendor-provided tools.
- 7. Reboot the system to load the new kernel driver.
- 8. Validate GPU functionality and ensure no regressions in graphics or compute workloads.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-0671 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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