dbcve.org
DdkApplication · Imaginationtech

CVE-2025-25179

HIGH · 7.8 CVSS v3.1 Published 2025-06-02
Fix available
A fix is available. Upgrade to after 24.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Software installed and run as a non-privileged user may conduct improper GPU system calls to subvert GPU HW to write to arbitrary physical memory pages.

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 confidence

A vulnerability in GPU system call handling allows non-privileged users to make improper GPU calls that subvert GPU hardware to write to arbitrary physical memory pages, enabling privilege escalation and potential arbitrary code execution.

MitigationApply vendor-specific patches for affected GPU drivers and hardware. Consider restricting non-privileged access to GPU resources until patches are deployed.

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
DdkApplication
Affected:<= 24.3

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Imagination Technologies GPU driver presence
    Check system for Imagination Technologies (PowerVR) GPU driver files or modules. Look for driver components associated with the DDK in the kernel module directory or driver package location.
    Affected if Imagination Technologies GPU driver is installed on the system
  2. Determine installed DDK version
    Query the installed driver version through system utilities (such as 'modinfo' for kernel modules, driver management tools, or driver version information in system logs). Compare the version number against the <= 24.3 threshold.
    Affected if The DDK version is 24.3 or lower
  3. Verify non-privileged GPU access is possible
    Check if unprivileged users have access to GPU device files or can invoke GPU system calls. Review permissions on GPU device nodes (commonly in /dev) and group memberships that grant GPU access.
    Affected if Non-privileged (non-root) users have direct access to GPU resources or can make GPU system calls without elevated privileges
  4. Confirm GPU hardware is in use
    Verify that Imagination Technologies GPU hardware is actively in use by the system. Check system hardware inventory or active device status.
    Affected if The system actively uses Imagination Technologies GPU hardware with the affected driver

The system is affected if it has Imagination Technologies GPU driver version 24.3 or lower installed AND non-privileged users can access GPU resources, allowing them to exploit the memory write vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 24.3
Interim mitigation

Apply vendor-specific patches for affected GPU drivers and hardware. Consider restricting non-privileged access to GPU resources until patches are deployed.

Recommended fix Moderate confidence

DDK version greater than 24.3 (contact Imagination Technologies for exact patched release)

  1. 1. Identify the current DDK (Driver Development Kit) version in use by checking the installed GPU driver package.
  2. 2. Contact Imagination Technologies directly or visit their official support portal at www.imaginationtech.com to obtain the patched DDK version.
  3. 3. Before applying any update, ensure all critical data is backed up.
  4. 4. Apply the updated DDK version following Imagination Technologies' installation documentation.
  5. 5. Verify the update was successful and test GPU functionality to confirm the vulnerability is mitigated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ddk Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25179 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25179 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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