# CVE-2024-46975: GPU DDK - rgxfw_write_robustness_buffer allows arbitrary catreg set mapping

> A malicious kernel in a guest VM can exploit shared GPU memory to access another guest's virtualized GPU memory, leading to privilege escalation.

- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/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:** 22 Feb 2025
- **Updated:** 24 Feb 2025
- **Also known as:** A-385657784, ASB-A-385657784, GHSA-2rfp-wr5h-6q7x

## What is CVE-2024-46975?

CVE-2024-46975 is a high-severity vulnerability in Imagination Technologies Graphics DDK, published on 22 Feb 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 into another Guest's virtualised GPU memory.

Weakness: CWE-270 (Privilege Context Switching Error)

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


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

Apply the vendor's patch.

## Is CVE-2024-46975 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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