# CVE-2026-49746: GPU DDK - Dimension Mismatch and Integer Truncation in PMRDevPhysAddrOSMem

> A non-privileged user can trigger out-of-bounds reads and use-after-free in the GPU driver, potentially leading to kernel memory access and privilege escalation.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** A-505486464, ASB-A-505486464, GHSA-xxq2-97gh-5p37

## What is CVE-2026-49746?

CVE-2026-49746 is a high-severity memory corruption vulnerability in Imagination Technologies Graphics DDK, published on 7 Aug 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 OOB read kernel memory access and in certain cases cause GPU UAF of arbitrary pages.

Incorrect validation of array index can lead to OOB read and potentially to GPU UAF of arbitrary pages.

Weakness: CWE-823 (Use of Out-of-range Pointer Offset)

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


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

Apply the vendor's patch.

## Is CVE-2026-49746 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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