CVE-2025-6573 GPU DDK - RGXFW_CTL.pui8FWScratchBuf Leak/Overwrite
Critical 9.8
Published
Updated
Check this codebase for CVE-2025-6573 and fix it if it is affected.
What it is: CVE-2025-6573 is a critical vulnerability in Imagination Technologies Graphics DDK, published on 8 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6573 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-2025-6573/ (Markdown: https://insights.sbomify.com/CVE-2025-6573/index.md)
A vulnerability in the Android GPU driver allows kernel software to leak information from the trusted execution environment.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-6573?
CVE-2025-6573 is a critical vulnerability in Imagination Technologies Graphics DDK, published on 8 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Kernel software installed and running inside an untrusted/rich execution environment (REE) could leak information from the trusted execution environment (TEE).
Weakness: CWE-280
Which versions are affected by CVE-2025-6573?
How do I fix CVE-2025-6573?
Apply the vendor's patch.
Is CVE-2025-6573 being exploited?
There is no known exploitation of CVE-2025-6573 in the wild and no public exploit code.
Sources
Also known as A-384999601, ASB-A-384999601, GHSA-x5ph-c3x5-4wmg.