Mali GPU Kernel Driver allows improper GPU processing operations
Noroxi assessment
Priority: Monitor (action score 16/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system 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 r54p2, r55p0; Arm Ltd Valhall GPU Kernel Driver r54p2, r55p0.
Low priority for now. Upgrade to Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver r54p2, r55p0; Arm Ltd Valhall GPU Kernel Driver r54p2, r55p0 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 Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform improper GPU processing operations to gain access to already freed memory.This issue affects Valhall GPU Kernel Driver: from r53p0 through r54p1; Arm 5th Gen GPU Architecture Kernel Driver: from r53p0 through r54p1.
- Published
- Dec 1, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-416
Report tools
Action score
16
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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
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 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 | valhall gpu kernel driver | cpe:2.3:a:arm:valhall_gpu_kernel_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 kernel driverr53p0 and later · before r54p2
- arm valhall gpu kernel driverr53p0 and later · before r54p2
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
- r53p0 and later · up to and including r54p1affected · patchfixed in r54p2, r55p0
Arm Ltd Valhall GPU Kernel Driver
- r53p0 and later · up to and including r54p1affected · patchfixed in r54p2, r55p0
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 aKEV43Plan
- CVE-2023-6143Mali GPU Kernel Driver allows improper GPU memory processing operations33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-3212Sep 8, 2025 · Mali GPU Kernel Driver allows access to already freed memory21Monitor
- ← EarlierCVE-2025-2879Dec 1, 2025 · Mali GPU Kernel Driver allows improper GPU processing operations20Monitor
- ← EarlierCVE-2025-6349Dec 1, 2025 · Mali GPU Kernel Driver allows improper GPU memory 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 | r54p2 | Vendor (CNA) |
| Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver | r55p0 | Vendor (CNA) |
| Arm Ltd Valhall GPU Kernel Driver | r54p2 | Vendor (CNA) |
| Arm Ltd Valhall GPU Kernel Driver | r55p0 | Vendor (CNA) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:7 | 2026-08-06 |
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.
- Published
- First PoC+248 d
- TodayOct 19, 2026+322 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Pumpkin (@u1f383)DEVCORE Research Teamfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-0073182 days apartMali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- CVE-2025-0819182 days apartMali GPU Kernel Driver allows access to already freed memory31Monitor
- CVE-2025-0072213 days apartMali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- CVE-2025-0427213 days apartMali GPU Kernel Driver allows access to already freed memory31Monitor
- CVE-2025-0015301 days apartMali GPU Kernel Driver allows improper GPU processing operations31Monitor
- CVE-2024-3655454 days apartMali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system 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
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/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 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.