CVE-2026-9034
Awaiting Analysis
Awaiting Analysis - Queue
Use After Free in Arm GPU Userspace Drivers
Vulnerability report for CVE-2026-9034, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-09-08
Last updated on: 2026-09-08
Assigner: Arm Limited
Description
Description
Use After Free vulnerability in Arm Ltd Bifrost GPU Userspace Driver, 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 Bifrost GPU Userspace Driver: from r42p0 through r49p5, from r50p0 through r51p0, from r54p1 through r54p3; Valhall GPU Userspace Driver: from r42p0 through r49p5, from r50p0 through r54p3, r55p0; Arm 5th Gen GPU Architecture Userspace Driver: from r42p0 through r49p5, from r50p0 through r54p3, r55p0.
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| arm_ltd | bifrost_gpu_userspace_driver | From r42p0 (inc) to r49p5 (inc) |
| arm_ltd | bifrost_gpu_userspace_driver | From r50p0 (inc) to r51p0 (inc) |
| arm_ltd | bifrost_gpu_userspace_driver | From r54p1 (inc) to r54p3 (inc) |
| arm_ltd | valhall_gpu_userspace_driver | From r42p0 (inc) to r49p5 (inc) |
| arm_ltd | valhall_gpu_userspace_driver | From r50p0 (inc) to r54p3 (inc) |
| arm_ltd | valhall_gpu_userspace_driver | From r55p0 (inc) |
| arm_ltd | arm_5th_gen_gpu_architecture_userspace_driver | From r42p0 (inc) to r49p5 (inc) |
| arm_ltd | arm_5th_gen_gpu_architecture_userspace_driver | From r50p0 (inc) to r54p3 (inc) |
| arm_ltd | arm_5th_gen_gpu_architecture_userspace_driver | From r55p0 (inc) |
Helpful Resources
Exploitability
CWE
KEV
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
