CVE-2025-3212: Mali GPU Kernel Driver allows access to already freed memory
Noroxi assessment
Priority: Monitor (action score 21/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.34% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver r54p1; Arm Ltd Bifrost GPU Kernel Driver r54p1; Arm Ltd Valhall GPU Kernel Driver r54p1.
Low priority for now. Upgrade to Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver r54p1; Arm Ltd Bifrost GPU Kernel Driver r54p1; Arm Ltd Valhall GPU Kernel Driver 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 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 gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r41p0 through r49p4, from r50p0 through r51p0; Valhall GPU Kernel Driver: from r41p0 through r49p4, from r50p0 through r54p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p4, from r50p0 through r54p0.
- Published
- Sep 8, 2025
- Updated
- Nov 3, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-416
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.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.
Is your version affected? Check itNoroxi 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 helpAffected 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 kernel driver | cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver |
| arm | bifrost gpu kernel driver | cpe:2.3:a:arm:bifrost_gpu_kernel_driver |
| arm | valhall gpu kernel driver | cpe:2.3:a:arm:valhall_gpu_kernel_driver |
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 Kernel Driver
- r41p0 and later · up to and including r49p4affected · patch
- r50p0 and later · up to and including r54p0affected · patchfixed in r54p1
Arm Ltd Bifrost GPU Kernel Driver
- r41p0 and later · up to and including r49p4affected · patch
- r50p0 and later · up to and including r51p0affected · patchfixed in r54p1
Arm Ltd Valhall GPU Kernel Driver
- r41p0 and later · up to and including r49p4affected · patch
- r50p0 and later · up to and including r54p0affected · patchfixed in r54p1
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- arm 5th gen gpu architecture kernel driverr41p0 and later · up to r49p4 inclusive
- arm 5th gen gpu architecture kernel driverr50p0 and later · before r54p1
- arm bifrost gpu kernel driverr41p0 and later · up to r49p4 inclusive
- arm bifrost gpu kernel driverr50p0 and later · before r54p1
- arm valhall gpu kernel driverr41p0 and later · up to r49p4 inclusive
- arm valhall gpu kernel driverr50p0 and later · before r54p1
Same product
arm: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4211Mali GPU Kernel Driver Allows Improper GPU Memory Processing OperationsKEV52Plan
- CVE-2023-26083Memory leak vulnerability in Mali GPU Kernel Driver in Midgard GPU Kernel Driver all versions from r6p0 - r32p0, Bifrost GPU Kernel Driver…KEV43Plan
- CVE-2023-6143Mali GPU Kernel Driver allows improper GPU memory processing operations33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-0073Jun 2, 2025 · Mali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- ← EarlierCVE-2025-0819Jun 2, 2025 · Mali GPU Kernel Driver allows access to already freed memory31Monitor
- Later →CVE-2025-2879Dec 1, 2025 · Mali GPU Kernel Driver allows improper GPU processing operations20Monitor
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 Kernel Driver | r54p1 | Vendor (CNA) |
| Arm Ltd Bifrost GPU Kernel Driver | r54p1 | Vendor (CNA) |
| Arm Ltd Valhall GPU Kernel 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-007398 days apartMali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- CVE-2025-081998 days apartMali GPU Kernel Driver allows access to already freed memory31Monitor
- CVE-2025-0072129 days apartMali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- CVE-2025-0427129 days apartMali GPU Kernel Driver allows access to already freed memory31Monitor
- CVE-2025-0015217 days apartMali GPU Kernel Driver allows improper GPU processing operations31Monitor
- CVE-2024-3655370 days apartMali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.