CVE-2025-0073: Arm Valhall GPU Kernel Driver · Use After Free
Affects Arm Valhall GPU Kernel DriverSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2025-0073 effectively, European organizations should: 1) Immediately inventory and identify all systems utilizing the affected Valhall GPU Kernel Driver versions (r53p0 to before r54p0). 2) Monitor Arm Ltd's official channels for the release of security patches or updated driver versions and prioritize timely deployment once available. 3) Implement strict access controls to limit local user privileges, reducing the risk of exploitation by non-privileged users. 4) Employ kernel-level exploit mitigation techniques such as Kernel Address Space Layout Randomization (KASLR) and Kernel Page-Table Isolation (KPTI) where supported to increase exploitation difficulty. 5) Use application whitelisting and endpoint detection and response (EDR) solutions to detect anomalous behavior indicative of exploitation attempts. 6) For environments where patching is delayed, consider isolating vulnerable systems or restricting access to trusted users only. 7) Conduct regular security audits and penetration testing focusing on GPU driver vulnerabilities and privilege escalation paths. 8) Educate system administrators and security teams about the specific risks associated with GPU driver vulnerabilities to enhance incident response readiness.
Description
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 memory processing operations to gain access to already freed memory.This issue affects Valhall GPU Kernel Driver: from r53p0 before r54p0; Arm 5th Gen GPU Architecture Kernel Driver: from r53p0 before r54p0.