dbcve.org
DdkApplication · Imaginationtech

CVE-2025-58410

HIGH · 7.5 CVSS v3.1 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 gain write permissions to memory buffers exported as read-only. This is caused by improper handling of the memory protections for the buffer resource.

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 software allows non-privileged users to make improper system calls that bypass memory protection controls, enabling write access to buffers that should be read-only. The root cause is improper validation of memory protection flags when handling GPU buffer resources.

MitigationFix the buffer resource memory protection handling to properly enforce read-only permissions and validate memory protection flags before GPU system calls.

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:= 23.3= 24.1= 24.2= 24.3= 25.1= 25.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify Imagination Technologies GPU driver installation
    Query the system for installed GPU drivers. On Linux, check /sys/class/drm or use tools like lspci | grep -i vga. On Windows, check Device Manager under Display adapters. Look for Imagination Technologies or PowerVR GPU entries.
    Affected if Imagination Technologies (PowerVR) GPU driver is present in the system
  2. Determine installed DDK version
    Use the driver vendor's version query tool or check driver package metadata. On Linux, this may be available through /proc driver files or glxinfo. Look for version strings matching 23.3, 24.1, 24.2, 24.3, 25.1, or 25.2.
    Affected if The installed DDK version matches any of: 23.3, 24.1, 24.2, 24.3, 25.1, or 25.2
  3. Verify GPU buffer resource usage with read-only protection
    Review application or workload configurations that create GPU buffer resources with read-only memory protection flags. Inspect API calls or resource definitions that specify GPU_BUFFER_USAGE_READ_ONLY or equivalent flags.
    Affected if Applications or workloads are creating GPU buffers with read-only protection flags, and the vulnerable DDK version is in use

The environment is affected if Imagination Technologies DDK version 23.3, 24.1, 24.2, 24.3, 25.1, or 25.2 is installed and applications utilize GPU buffer resources with read-only memory protection flags.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix the buffer resource memory protection handling to properly enforce read-only permissions and validate memory protection flags before GPU system calls.

Recommended fix Moderate confidence

PowerVR GPU Driver (DDK) 24.4 or later

  1. Identify the Imagination Technologies PowerVR GPU driver (DDK) version currently installed using driver enumeration or system documentation
  2. Download the latest PowerVR GPU driver package from Imagination Technologies' official support portal at www.imaginationtech.com
  3. Install the updated driver package following the vendor's installation instructions for your specific platform
  4. Verify the installed driver version matches the patched release
  5. Test GPU functionality to confirm the memory protection fix is applied and working correctly
Caveat Review release notes for any API changes between 24.3 and the target version; some legacy GPU features may have deprecated behavior

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

Fix this in Ddk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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