Quick answers
- Is CVE-2026-5729 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5729 being exploited in the wild.
- How severe is CVE-2026-5729?
- High severity, with a CVSS score of 7.8, published 8 September 2026.
- Which products and versions are affected?
- Arm 5th Gen GPU Architecture Kernel Driver r50p0 through r54p3, r55p0; Arm Valhall GPU Kernel Driver r50p0 through r54p3, r55p0.
- Is there a fix for CVE-2026-5729?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-5729 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-5729?
- Check whether you run Arm 5th Gen GPU Architecture Kernel Driver or Arm Valhall GPU Kernel Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a use-after-free vulnerability in Arm's Valhall GPU Kernel Driver and Arm 5th Gen GPU Architecture Kernel Driver. A local, non-privileged user process can perform crafted GPU processing operations to trigger access to freed memory regions. The vulnerability exists in versions r50p0 through r54p3 and r55p0 of both drivers. An attacker must have local access to submit GPU commands but requires no elevated privileges. Successful exploitation may lead to information disclosure, denial of service, or potentially arbitrary code execution within the GPU context.
Affected products
- Arm Valhall GPU Kernel Driver r50p0 through r54p3, r55p0
- Arm 5th Gen GPU Architecture Kernel Driver r50p0 through r54p3, r55p0
Timeline
- 2026-09-08: disclosed