# CVE-2024-52938: GPU DDK - rgxfw_pm_add_freelist_for_reconstruction OOB write

> A malicious kernel in a guest VM can trigger an out-of-bounds write in the GPU firmware, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 13 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** A-380397760, ASB-A-380397760, GHSA-3vv9-8w9f-p9ff

## What is CVE-2024-52938?

CVE-2024-52938 is a high-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, with no action from the victim.

### Official description

Kernel software installed and running inside a Guest VM may post improper commands to the GPU Firmware to subvert reconstruction activities to trigger a write of 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-52938?


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

Apply the vendor's patch.

## Is CVE-2024-52938 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52938 is a high-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, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52938 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-52938/ (Markdown: https://insights.sbomify.com/CVE-2024-52938/index.md)
```

## Sources

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

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