# CVE-2026-45204: Null dereference in Graphics DDK

> A local attacker can trigger a kernel null pointer dereference in the GPU driver, causing system instability and denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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:** No
- **Published:** 7 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-6g52-rc6p-5579

## What is CVE-2026-45204?

CVE-2026-45204 is a medium-severity 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 trigger OOB access and kernel null pointer dereference in an error path.

Null pointer dereference occurs in an error path of a function running in kernel thread of execution leading to kernel exceptions, platform instability and denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

No fix has been published for CVE-2026-45204 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-45204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45204 is a medium-severity 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-45204 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-45204/ (Markdown: https://insights.sbomify.com/CVE-2026-45204/index.md)
```

## Sources

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

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