dbcve.org
DdkApplication · Imaginationtech

CVE-2025-58411

HIGH · 8.8 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 25.3 or later.
See remediation →
90/100
Remediation priority · Urgent
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 cause mismanagement of resources reference counting creating a potential use after free scenario. Improper resource management and reference counting on an internal resource caused scenario where potential write use after free was present.

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 use-after-free vulnerability exists in GPU-related software where improper resource management and reference counting on internal GPU resources allows non-privileged users to trigger a condition where memory is accessed after being freed through improper GPU system calls.

MitigationContact the vendor for the specific patch addressing the reference counting logic in the GPU software; until then, restrict access to the affected software and monitor for unusual GPU system call patterns.

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:< 25.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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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. Locate Imaginationtech Ddk installation
    Search for Imaginationtech GPU driver/DDK components on the system. Common locations include /usr/lib, /lib/modules, or vendor-specific directories. Use commands like 'find /usr -name "*imagination*"' or 'ls -la /dev/pvr*' to locate PowerVR GPU driver files and device nodes.
    Affected if Imaginationtech Ddk or PowerVR GPU driver files are present on the system
  2. Determine installed Ddk version
    Query the installed package version using system package managers (dpkg, rpm, pacman) or check version strings within driver binaries. Look for version information in driver files, or use 'modinfo' if loaded as a kernel module.
    Affected if Installed version is below 25.3 (e.g., 25.2, 25.1, etc.)
  3. Check GPU device node permissions
    Examine permissions on GPU device nodes (commonly /dev/pvr/* or similar Imaginationtech device paths). Use 'ls -la /dev/pvr*' or equivalent to see if read/write access is granted to non-root users.
    Affected if Non-privileged users have read/write access to GPU device nodes
  4. Verify user-space GPU API access
    Check if unprivileged users can access GPU user-space libraries or APIs. Review permissions on /usr/lib/libPVR* or similar shared objects, and check group membership or ACLs that allow standard users to invoke GPU-related system calls.
    Affected if Non-privileged users can directly invoke GPU system calls or APIs without special privileges

System is affected if Imaginationtech Ddk version is lower than 25.3 AND non-privileged users have access to GPU device nodes or can invoke GPU system calls.

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 25.3 or later
Fixed in 25.3
Interim mitigation

Contact the vendor for the specific patch addressing the reference counting logic in the GPU software; until then, restrict access to the affected software and monitor for unusual GPU system call patterns.

Recommended fix Moderate confidence

Ddk 25.3

  1. Identify the current Ddk version installed in your environment by checking the driver package or using appropriate diagnostic tools
  2. Download Ddk version 25.3 or later from the official Imagination Technologies source (www.imitationtech.com)
  3. Review release notes for version 25.3 to understand any changes or requirements
  4. Backup current driver configuration and any dependent applications
  5. Install Ddk 25.3 following the standard installation procedure for your environment
  6. Verify the new version is correctly installed and the driver loads without errors
  7. Test GPU-dependent applications to confirm normal operation
Caveat None explicitly mentioned in the provided description; standard driver upgrade precautions apply

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

Fix this in Ddk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58411 — 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-58411 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