GPU DDK - Write UAF due to missing cleanup reference for abort command submitted via PVRSRVRGXKickTA3DKM
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The affected software is the GPU driver development kit (DDK) used with graphics hardware, specifically its GPU command submission handling. A non-privileged local application could exploit a memory management flaw to free memory the GPU is still using, then replace it, potentially allowing reads or writes to arbitrary physical memory.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Software installed and run as a non-privileged user may conduct improper GPU system calls to free memory in still in use, replace with another allocation and cause arbitrary memory reads or writes to physical memory pages. A memory buffer managed by a CPU thread of control (driver) and accessed by a GPU thread of control (firmware) can be freed while in use. Software installed and run as a non-privileged user may replace that buffer with another and replace a shared resource (memory page address list) managed by the CPU thread of control (driver) leading to the GPU accessing memory not managed by the CPU thread of control (driver).
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Imagination Technologies Graphics DDK
From 25.1 RTM2 · through 25.3 RTM