CVE-2025-10865
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 · uneditedSoftware installed and run as a non-privileged user may conduct improper GPU system calls to cause mismanagement of reference counting to cause a potential use after free. Improper reference counting on an internal resource caused scenario where potential for 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 confidenceA use-after-free vulnerability exists in GPU-related software where improper reference counting on internal resources during GPU system calls allows a non-privileged user to trigger a condition where memory is accessed after being freed. This is a memory safety flaw in the reference counting logic for GPU resources.
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< 25.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Imaginationtech GPU driver installationCheck if Imaginationtech GPU drivers (Ddk) are present in the system by examining installed GPU drivers, kernel modules, or SDK packages. Look for components matching 'imagination' or 'powervr' branding.Affected if Imaginationtech GPU software is installed on the system
-
Determine installed Ddk versionLocate and inspect the installed Imaginationtech Ddk version. This may be found in driver package metadata, library version info, or by querying the GPU driver subsystem. Compare the version number against 25.3.Affected if The installed Ddk version is lower than 25.3
-
Verify GPU access for non-privileged usersCheck whether untrusted or non-privileged user accounts have the ability to execute GPU-accelerated applications or make GPU system calls. Review user group memberships and permissions related to GPU device access.Affected if Non-privileged users can access or utilize GPU functionality
-
Confirm active GPU workloadDetermine if the system is actively using the GPU for any computational or rendering tasks. Monitor for active GPU processes, running graphics applications, or GPU compute workloads.Affected if GPU is actively being used by any application or process
The environment is affected if Imaginationtech Ddk version is below 25.3 AND the GPU is accessible to and being used by non-privileged users, enabling them to trigger the improper reference counting during GPU system calls.
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.
dbcve · scoped25.3
Apply vendor-supplied patches for the affected GPU software components. Until a patch is available, monitor for unusual GPU behavior and restrict untrusted users from running GPU-accelerated applications where possible.
Ddk 25.3
- Upgrade the Ddk (Device Driver Kit) to version 25.3 or later
- Verify the upgrade by checking the Ddk version post-installation
- Test the GPU functionality to ensure the use after free vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10865 — 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-10865 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