# CVE-2025-0468: GPU DDK - ui64RobustnessAddress can overwrite Freelist / HWRT (and bypass PMMETA)

> A non-privileged user can exploit GPU system calls to write to arbitrary physical memory, potentially escalating privileges or executing code on Android devices.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Apr 2025
- **Updated:** 7 Apr 2025
- **Also known as:** A-382558918, ASB-A-382558918, GHSA-88rv-3gw6-829j

## What is CVE-2025-0468?

CVE-2025-0468 is a high-severity vulnerability in Imagination Technologies Graphics DDK, published on 4 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Software installed and run as a non-privileged user may conduct improper GPU system calls to subvert GPU HW to write to arbitrary physical memory pages.

Under certain circumstances this exploit could be used to corrupt data pages not allocated by the GPU driver but memory pages in use by the kernel and drivers running on the platform altering their behaviour.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2025-0468?


## How do I fix CVE-2025-0468?

Apply the vendor's patch.

## Is CVE-2025-0468 being exploited?

There is no known exploitation of CVE-2025-0468 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0468 and fix it if it is affected.

What it is: CVE-2025-0468 is a high-severity vulnerability in Imagination Technologies Graphics DDK, published on 4 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0468 in the wild and no public exploit code.

Affected product: Imagination Technologies Graphics DDK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-0468/ (Markdown: https://insights.sbomify.com/CVE-2025-0468/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0468
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0468
- OSV: https://osv.dev/vulnerability/CVE-2025-0468

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-0468/
Summaries are generated and may contain mistakes; the official description above is the record.