CVE-2025-0467
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKernel 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA vulnerability in GPU virtualization allows guest VM kernel software to exploit memory shared with the GPU Firmware, enabling writes outside the guest's virtualized GPU memory boundaries. This constitutes a VM escape condition where a compromised or malicious guest can potentially access host system resources through the GPU.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 24.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Imagination Technologies GPU in systemCheck system hardware inventory or driver information for Imagination Technologies GPU components. On Linux, 'lspci' or 'lsmod' may show 'powervr' or 'imagination' related modules.Affected if An Imagination Technologies GPU is present and the DDK version is 24.3 or lower
-
Determine DDK versionCheck the installed GPU driver/SDK package version. The version may be visible in driver files, system logs, or via 'modinfo' for GPU kernel modules.Affected if The installed DDK version is 24.3 or any version <= 24.3
-
Verify GPU virtualization or passthrough is enabledCheck hypervisor configuration (e.g., libvirt XML, VMware settings, Hyper-V settings) or host system for active GPU passthrough or virtualization assignments to VMs.Affected if GPU passthrough or GPU virtualization is actively configured and the guest VM has direct or near-direct access to the GPU
-
Confirm guest VM has GPU accessInspect the VM configuration to determine whether the vulnerable GPU is exposed to any guest VM, either through paravirtualization, passthrough, or vGPU mechanisms.Affected if A guest VM has been granted access to the Imagination Technologies GPU and the DDK version is <= 24.3
A system is affected if it runs an Imagination Technologies GPU with DDK version 24.3 or lower and has GPU virtualization or passthrough enabled that exposes the GPU to guest VMs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-specific patches to GPU firmware and hypervisor software. Consider disabling GPU passthrough or virtualization features if not required, and isolate GPU workloads in trusted VMs.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0467 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data