NVD / CVE Program· CNA Arm

CVE-2025-0932: Mali GPU Userspace Driver allows access to already freed memory

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver r49p4, r54p1; Arm Ltd Bifrost GPU Userspace Driver r49p4, r54p1; Arm Ltd Valhall GPU Userspace Driver r49p4, r54p1.

Low priority for now. Upgrade to Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver r49p4, r54p1; Arm Ltd Bifrost GPU Userspace Driver r49p4, r54p1; Arm Ltd Valhall GPU Userspace Driver r49p4, r54p1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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 gain access to already freed memory.This issue affects Bifrost GPU Userspace Driver: from r48p0 through r49p3, from r50p0 through r51p0; Valhall GPU Userspace Driver: from r48p0 through r49p3, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Userspace Driver: from r48p0 through r49p3, from r50p0 through r54p0.

MediumCVSS 4.3 · v3.1—No exploit Fix available

Memory safety

BDU:2025-11286

Published: Aug 4, 2025
Updated: Jun 17, 2026
EPSS: 0.3% · 22th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
arm	5th gen gpu architecture userspace driver	cpe:2.3:a:arm:5th_gen_gpu_architecture_userspace_driver
arm	bifrost gpu userspace driver	cpe:2.3:a:arm:bifrost_gpu_userspace_driver
arm	valhall gpu userspace driver	cpe:2.3:a:arm:valhall_gpu_userspace_driver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

arm 5th gen gpu architecture userspace driverr48p0 and later · before r49p4
arm 5th gen gpu architecture userspace driverr50p0 and later · before r54p1
arm bifrost gpu userspace driverr48p0 and later · before r49p4
arm bifrost gpu userspace driverr50p0 and later · before r54p1
arm valhall gpu userspace driverr48p0 and later · before r49p4
arm valhall gpu userspace driverr50p0 and later · before r54p1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Arm). Independent of NVD's CPE analysis and usually ahead of it.

Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver
- r48p0 and later · up to and including r49p3affected · patchfixed in r49p4
- r50p0 and later · up to and including r54p0affected · patchfixed in r54p1
Arm Ltd Bifrost GPU Userspace Driver
- r48p0 and later · up to and including r49p3affected · patchfixed in r49p4
- r50p0 and later · up to and including r51p0affected · patchfixed in r54p1
Arm Ltd Valhall GPU Userspace Driver
- r48p0 and later · up to and including r49p3affected · patchfixed in r49p4
- r50p0 and later · up to and including r54p0affected · patchfixed in r54p1

Same product

arm: all records

Other highest-scoring records for the same primary product.

CVE-2025-1246Mali GPU Userspace Driver allows an Out-of-Bounds access
31Monitor
CVE-2025-0050Mali GPU Userspace Driver allows an Out-of-Bounds access
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver	r49p4	Vendor (CNA)
Arm Ltd Arm 5th Gen GPU Architecture Userspace Driver	r54p1	Vendor (CNA)
Arm Ltd Bifrost GPU Userspace Driver	r49p4	Vendor (CNA)
Arm Ltd Bifrost GPU Userspace Driver	r54p1	Vendor (CNA)
Arm Ltd Valhall GPU Userspace Driver	r49p4	Vendor (CNA)
Arm Ltd Valhall GPU Userspace Driver	r54p1	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Lukas Bernhardfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

ArmIntigriti · paid · up to $20,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

developer.arm.com/documentation/110626/latest/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records