Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local unprivileged code execution
-
DeliveryIssue crafted GPU memory allocation sequence
-
ExploitTrigger premature free of GPU memory region
-
ExecutionIssue valid GPU operation referencing freed region
-
ImpactRead or overwrite freed kernel memory contents
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must have local unprivileged code execution on a device whose GPU kernel driver falls within the affected version ranges for Bifrost, Valhall, or Arm 5th Gen architecture. Exploitation requires the ability to make GPU memory processing API calls, which is standard for any application on Android or Linux systems with Mali GPU access - no special privilege or non-default configuration is needed beyond running code on the affected device. The CVSS vector (AV:L/PR:L) confirms that network-reachable or unauthenticated remote exploitation is not possible; an attacker must already be executing code on the target system. Exploitation is not automatable per SSVC, meaning a tailored sequence of GPU operations is needed rather than a fire-and-forget payload. |
| Impact | CVSS 3.1 scores this at 4.4 (Medium), reflecting AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N - a local, low-complexity, low-privilege attack with limited impact and no scope change. SSVC corroborates the restrained picture: exploitation is rated 'none,' the attack is not automatable (requires direct local process interaction with the GPU), and technical impact is 'partial.' No KEV listing, no public proof-of-concept, and no EPSS score is provided, meaning real-world exploitation probability cannot be independently quantified. The CVSS Availability score of N conflicts with the 'Denial Of Service' tag in the input metadata; the vendor's own advisory rates A:N, and the description describes memory access, not a crash path - the DoS tag appears to be an error. While UAF in a kernel driver carries theoretical escalation risk, the vendor's CVSS and scope-unchanged assessment suggest the freed memory region is bounded within the driver's own allocations rather than arbitrary kernel memory. This is a credible but low-urgency vulnerability: patch during normal maintenance cycles; no evidence of active exploitation warrants emergency response. |
| Exploit ScenarioDerived | An unprivileged application running on an Android or embedded Linux device with an Arm Bifrost, Valhall, or 5th Gen Mali GPU issues a sequence of GPU memory operations that causes the kernel driver to free a memory region while retaining a live reference to it. A subsequent valid GPU processing call then dereferences the stale pointer, allowing the application to read or modify the contents of the freed memory region - which may contain residual data from prior GPU workloads of other processes. No public proof-of-concept has been identified, and exploitation requires local code execution on the target device. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU kernel drivers allows a local unprivileged process to access already-freed GPU memory through valid GPU memory processing operations, resulting in limited confidentiality and integrity impact against the kernel driver. The flaw spans a wide range of driver versions across all three GPU architectures, affecting the enormous ecosystem of Android and embedded devices powered by Arm Mali GPUs. No public exploit or active exploitation has been identified; SSVC rates technical impact as partial and exploitation as none at time of analysis.
RemediationAI
Consult the Arm security advisory at https://support.arm.com/documentation/111552/1-0/?lang=en for the specific patched driver revisions for each GPU architecture family. OEM and device vendors (e.g., MediaTek, Samsung LSI, Google for Pixel) typically integrate Arm's upstream driver fixes into their own BSP releases; end users should apply the latest firmware or OS update from their device manufacturer. For Android deployments, confirm that monthly Security Bulletins (Google or OEM) include the fixed driver version. As a compensating control where patching is infeasible, restricting untrusted application access to GPU compute APIs (e.g., through SELinux policy tightening or container-level GPU resource isolation) reduces the attack surface, though this may break legitimate GPU-accelerated workloads. A patched driver version is not independently confirmed from the available reference data - consult the Arm advisory directly.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the kernel-mode GPU driver components for three Arm GPU microarchitecture families: Bifrost (cpe:2.3:a:arm_ltd:bifrost_gpu_kernel_driver), Valhall (cpe:2.3:a:arm_ltd:valhall_gpu_kernel_driver), and Arm 5th Gen GPU Architecture (cpe:2.3:a:arm_ltd:arm_5th_gen_gpu_architecture_kernel_driver). CWE-416 (Use After Free) arises when the driver fails to invalidate a memory reference after freeing the associated GPU memory region; a subsequent, otherwise-valid GPU operation dereferences the stale pointer and reaches the freed buffer. Because this occurs in a kernel driver, the freed memory may contain sensitive kernel or cross-process data, explaining the C:L/I:L impact. The flaw is local and requires only the privileges of a normal unprivileged user capable of making GPU API calls - typical for any app on an Android device using the Mali GPU stack.
Know when Bifrost Gpu Kernel Driver gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Local unprivileged access with low complexity; limited read/write to freed memory within driver scope; no availability impact per vendor assessment.
Primary rating from Vendor (Arm).
CVSS VectorVendor: Arm
Lifecycle Timeline
2DescriptionCVE.org
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 process to perform valid GPU memory processing operations to access already freed memory.
This issue affects Bifrost GPU Kernel Driver: from r41p0 through r49p5, from r50p0 through r51p0, from r54p1 through r54p2; Valhall GPU Kernel Driver: from r41p0 through r49p5, from r50p0 through r54p3, r55p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p5, from r50p0 through r54p3, r55p0.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
More in Bifrost Gpu Kernel Driver
View allThe Arm Mali GPU kernel driver allows unprivileged users to access freed memory because GPU memory operations are mishan
The Arm Mali GPU kernel driver allows privilege escalation or information disclosure because GPU memory operations are m
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Ge
Arm Mali GPU Kernel Driver has a use-after-free: Midgard r28p0 through r29p0 before r30p0, Bifrost r17p0 through r23p0 b
Arm Mali GPU Kernel Driver (Midgard r4p0 through r31p0, Bifrost r0p0 through r36p0 before r37p0, and Valhall r19p0 throu
. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch ava
The Arm Mali GPU kernel driver allows privilege escalation or a denial of service (memory corruption) because an unprivi
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers enables a local unprivileged proce
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture kernel drivers allows a local non-privileged proc
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Ge
A security vulnerability in Arm Ltd Bifrost GPU Kernel Driver (CVSS 7.8) that allows a local non-privileged user process
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Ge
EUVD-2026-72793
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB