# CVE-2024-52937: GPU DDK - rgxfw_kernel_CMD_DISABLE_ZSSTORE OOB write via ui32WriteOffsetOfDisableZSStore

> A malicious kernel in a guest VM can exploit an out-of-bounds write in the GPU firmware to execute code or escalate privileges on Android devices.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** A-381273105, ASB-A-381273105, GHSA-mhhc-7vg8-h992

## What is CVE-2024-52937?

CVE-2024-52937 is a medium-severity memory corruption vulnerability in Imagination Technologies Graphics DDK, published on 13 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Kernel software installed and running inside a Guest VM may exploit memory shared with the GPU Firmware to write data outside the Guest's virtualised GPU memory.

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

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


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

Apply the vendor's patch.

## Is CVE-2024-52937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52937 is a medium-severity memory corruption vulnerability in Imagination Technologies Graphics DDK, published on 13 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-52937 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-52937/ (Markdown: https://insights.sbomify.com/CVE-2024-52937/index.md)
```

## Sources

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

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