# CVE-2026-34192: GPU DDK - _MMU_AllocLevel error recovery paths leave dangling page table entries

> A non-privileged user can trigger a use-after-free in the GPU driver via improper system calls, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** A-491040696, ASB-A-491040696, GHSA-q7pr-p3c5-mgvj

## What is CVE-2026-34192?

CVE-2026-34192 is a high-severity use after free vulnerability in Imagination Technologies Graphics DDK, published on 19 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 an error path leading to UAF of GPU page tables.

The vulnerability allows physical memory allocated for MMU page tables to be used after being freed. This was caused by an error path that would not cleanup properly before freeing the physical allocation.

Weakness: CWE-416 (Use After Free)

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


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

Apply the vendor's patch.

## Is CVE-2026-34192 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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