Skip to main content

Arm Mali GPU Driver CVE-2026-11891

| EUVDEUVD-2026-72801 MEDIUM
Use After Free (CWE-416)
2026-09-08 Arm GHSA-v44f-6g2r-3454
5.1
CVSS 3.1 · Vendor: Arm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Victim loads crafted WebGL/WebGPU content
  2. Delivery
    browser renderer submits GPU commands via userspace driver
  3. Exploit
    driver frees GPU memory object prematurely
  4. Execution
    subsequent GPU operation dereferences freed pointer
  5. Persist
    attacker reads or corrupts freed memory region
  6. Impact
    limited data disclosure or integrity impact

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 vulnerable device must use an Arm Valhall or 5th Gen GPU Architecture userspace driver in the affected version range (r46p0-r49p5, r50p0-r54p3, or r55p0). The attacker must be able to submit GPU processing operations to the driver from a non-privileged process - this is satisfied by a local user-mode application or, notably, by WebGL/WebGPU APIs accessible from a browser tab. No special system configuration or elevated privileges are required (PR:N per CVSS), but the attack is constrained to local execution context (AV:L); remote exploitation requires a local vector such as a browser rendering malicious web content. The freed memory access is bounded to GPU allocator regions and does not provide arbitrary kernel or full-process memory read/write.

Impact

CVSS 3.1 scores this at 5.1 (Medium) with vector AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. The local attack vector (AV:L) is appropriate because the exploit pathway runs through userspace GPU driver interfaces, but PR:N reflects that any unprivileged process - including a sandboxed browser renderer executing WebGL or WebGPU shaders - can trigger the flaw without requiring elevated privileges. The C:L/I:L impact pair indicates limited, not arbitrary, memory access - the freed memory region is bounded by GPU allocator behavior and is unlikely to yield full process memory disclosure. EPSS sits at 0.14% (4th percentile), consistent with a GPU driver memory corruption bug that requires crafted GPU workloads, not a trivial web-delivered exploit. No CISA KEV listing and no public POC have been identified. The 'Denial Of Service' tag in the metadata conflicts with CVSS A:N, which Arm set to No Availability Impact - this discrepancy is noted but the official Arm advisory scoring is treated as authoritative. Overall, this is a real but low-urgency finding: exploitable in principle via WebGL/WebGPU but requiring crafted GPU operations and yielding only partial memory access.

Exploit ScenarioDerived

An attacker serves a webpage containing a crafted WebGL or WebGPU shader workload to a victim browsing on an Android or embedded device powered by an Arm Valhall or 5th Gen GPU. The GPU userspace driver processes syntactically valid but carefully sequenced GPU commands that cause a freed memory region to be dereferenced, potentially leaking data from that region or corrupting adjacent allocations. No public proof-of-concept exists at time of analysis, and the crafting of such a GPU workload requires deep knowledge of Arm Mali driver internals.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 10, 2026

Use-after-free memory access in Arm's Valhall and 5th Gen GPU Architecture userspace drivers allows a non-privileged local process - including browser-hosted WebGL or WebGPU workloads - to read and write already-freed GPU memory regions, yielding limited confidentiality and integrity compromise. Arm reported this issue internally; no active exploitation has been identified. The wide deployment of Arm Mali GPU hardware in mobile and embedded SoCs makes the affected driver versions relevant across a large device population, though the limited CVSS impact scores constrain severity.

RemediationAI

Upgrade to an Arm GPU userspace driver release beyond r55p0 for the affected Valhall and 5th Gen GPU Architecture product lines. Consult Arm's official advisory at https://support.arm.com/documentation/111552/1-0/?lang=en for the specific patched release identifier, as the exact fixed version tag is not stated in the available references. SoC vendors (Qualcomm, MediaTek, Samsung, etc.) that license and redistribute Arm Mali drivers typically ship updated driver packages through OS security update channels (Android Security Bulletins); device operators should apply OEM firmware updates promptly. If a firmware update cannot be applied immediately, restricting access to GPU-accelerated browser features (e.g., disabling WebGL/WebGPU in browser policy or via flags) would reduce the attack surface at the cost of performance and compatibility regressions for GPU-heavy web content. Server or embedded environments that do not expose GPU interfaces to untrusted workloads have lower urgency.

Affected VersionsENISA

Arm 5th Gen GPU Architecture Userspace Driver r50p0 ≤r54p3
Arm 5th Gen GPU Architecture Userspace Driver r55p0
Valhall GPU Userspace Driver r55p0
Arm 5th Gen GPU Architecture Userspace Driver r46p0 ≤r49p5
Valhall GPU Userspace Driver r46p0 ≤r49p5
Valhall GPU Userspace Driver r50p0 ≤r54p3

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 affected components are the GPU userspace drivers for two Arm GPU microarchitecture generations: Valhall (Mali-G series, common in mid-to-high-end Android SoCs) and Arm's 5th Generation GPU Architecture (successor line). Userspace GPU drivers handle command-stream submission, memory mapping, and GPU-side object lifecycle; they run as non-privileged code but interact tightly with kernel-side GPU driver modules. CWE-416 (Use After Free) indicates that GPU-managed memory objects are freed while a reference to them still exists in driver state, allowing a crafted but syntactically valid sequence of GPU operations - including those issued through the browser's WebGL or WebGPU APIs - to dereference the dangling pointer and access the freed region. CPE data confirms the affected vendors as arm_ltd across both driver families (cpe:2.3:a:arm_ltd:valhall_gpu_userspace_driver and cpe:2.3:a:arm_ltd:arm_5th_gen_gpu_architecture_userspace_driver).

Know when Valhall Gpu Userspace 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

Vendor (Arm) PRIMARY 5.1 MEDIUM
AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 5.1 MEDIUM

Local attack via GPU userspace interface with no privileges required; limited memory access (C:L/I:L) consistent with UAF scope; no availability impact confirmed by Arm scoring.

3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Arm).

CVSS VectorVendor: Arm

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

3
CVSS changed
Sep 10, 2026 - 19:22 NVD
5.1 (MEDIUM)
CVE Published
Sep 08, 2026 - 14:21 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 08, 2026 - 14:21 cve.org
MEDIUM 5.1

DescriptionCVE.org

Use After Free vulnerability in Arm Ltd Valhall GPU Userspace Driver, Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver allows a non-privileged user process to perform valid GPU processing operations, including via WebGL or WebGPU, to access already freed memory.

This issue affects Valhall GPU Userspace Driver: from r46p0 through r49p5, from r50p0 through r54p3, r55p0; Arm 5th Gen GPU Architecture Userspace Driver: from r46p0 through r49p5, from r50p0 through r54p3, r55p0.

Threat Intelligence Overview

EPSS Score
0.1%
Top 96% exploitable
Prevalence
High
Arm Mali/Valhall GPUs power hundreds of millions of Android devices
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy