# CVE-2024-12576: GPU DDK - Untrusted app can crash firmware by forcing MCU access to non-aligned address

> A non-privileged app can crash GPU firmware by forcing misaligned memory access, freezing graphics output on Android devices.

- **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:** Yes
- **Published:** 7 Mar 2025
- **Updated:** 7 Mar 2025
- **Also known as:** A-384017663, ASB-A-384017663, GHSA-gx49-v8fg-qgrf

## What is CVE-2024-12576?

CVE-2024-12576 is a medium-severity denial of service vulnerability in Imagination Technologies Graphics DDK, published on 7 Mar 2025. 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 a crash of the FW running on the GPU freezing graphics output.

Weakness: CWE-822 (Untrusted Pointer Dereference)

## Which versions are affected by CVE-2024-12576?


## How do I fix CVE-2024-12576?

Apply the vendor's patch.

## Is CVE-2024-12576 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12576 and fix it if it is affected.

What it is: CVE-2024-12576 is a medium-severity denial of service vulnerability in Imagination Technologies Graphics DDK, published on 7 Mar 2025. 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-2024-12576 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-2024-12576/ (Markdown: https://insights.sbomify.com/CVE-2024-12576/index.md)
```

## Sources

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

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