# CVE-2025-1706: GPU DDK - Improper locking when accessing the pvr_exp_fence object

> A local attacker can exploit a use-after-free in the GPU driver to escalate privileges or execute code in the kernel.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2025
- **Updated:** 19 May 2025
- **Also known as:** A-389976559, ASB-A-389976559, GHSA-wq25-m95j-8rw5

## What is CVE-2025-1706?

CVE-2025-1706 is a high-severity use after free vulnerability in Imagination Technologies Graphics DDK, published on 17 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Software installed and run as a non-privileged user may conduct improper GPU system calls to trigger use-after-free kernel exceptions.

Weakness: CWE-416 (Use After Free)

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


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

Apply the vendor's patch.

## Is CVE-2025-1706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1706 is a high-severity use after free vulnerability in Imagination Technologies Graphics DDK, published on 17 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1706 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-1706/ (Markdown: https://insights.sbomify.com/CVE-2025-1706/index.md)
```

## Sources

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

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