# CVE-2026-34194: Use after free in Graphics DDK

> A non-privileged user can exploit a GPU driver flaw to read or write arbitrary physical memory, potentially leading to code execution or privilege escalation 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:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** A-489979337, ASB-A-489979337, GHSA-4fp7-72xg-c4hc

## What is CVE-2026-34194?

CVE-2026-34194 is a high-severity use after free vulnerability in Imagination Technologies Graphics DDK, published on 8 Jun 2026. 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 cause mismanagement of a mapping state maintained for a sparse memory allocation.

The product accidentally refers to the wrong memory due to the semantics of how math operations are implicitly scaled across buffers of different sizes.

Weakness: CWE-468 (Incorrect Pointer Scaling)

## Which versions are affected by CVE-2026-34194?


## How do I fix CVE-2026-34194?

Apply the vendor's patch.

## Is CVE-2026-34194 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34194 and fix it if it is affected.

What it is: CVE-2026-34194 is a high-severity use after free vulnerability in Imagination Technologies Graphics DDK, published on 8 Jun 2026. 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-2026-34194 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-2026-34194/ (Markdown: https://insights.sbomify.com/CVE-2026-34194/index.md)
```

## Sources

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

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