dbcve.org
DdkApplication · Imaginationtech

CVE-2025-46711

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-22
Fix available
A fix is available. Upgrade to after 25.1 or later.
See remediation →
57/100
Remediation priority · Elevated
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 trigger NULL pointer dereference kernel exceptions.

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 trigger NULL pointer dereference exceptions in the kernel by making improper GPU calls. This can cause kernel panics or denial-of-service conditions, potentially enabling local privilege escalation depending on the specific kernel context and driver implementation.

MitigationApply vendor-supplied GPU driver and kernel patches addressing improper input validation in GPU system call paths; restrict GPU access through sandboxing or resource limits for untrusted processes until patches are applied.

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:>= 1.17, <= 25.1

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 if Imaginationtech GPU driver is present
    Check for loaded GPU driver modules using 'lsmod | grep -i img' or 'lsmod | grep -i powervr' and examine /dev for GPU device nodes like /dev/pvr or /dev/mgc_gpu
    Affected if Imaginationtech GPU driver modules are loaded or GPU device nodes exist on the system
  2. Determine the installed DDK version
    Check the driver version via 'modinfo img-*/pvr.ko' or 'cat /sys/module/*/version' for the GPU module, or check /usr/src/ for DDK version directories
    Affected if The DDK version falls within >= 1.17 and <= 25.1
  3. Verify non-privileged user GPU access
    Check permissions on GPU device nodes (ls -la /dev/pvr* or /dev/mgc_gpu*) and review /etc/security/limits.conf for any GPU resource limits configured for untrusted users
    Affected if GPU device nodes are accessible to non-privileged users (world-readable/writable or group-accessible without proper restrictions)
  4. Confirm kernel exposure to GPU system calls
    Review audit logs or dmesg for recent NULL pointer dereference errors related to GPU operations, and check if sandboxing or seccomp filters are applied to processes making GPU calls
    Affected if Non-privileged processes can directly invoke GPU system calls without restrictive sandboxing

The system is affected if Imaginationtech DDK versions 1.17 through 25.1 are installed AND non-privileged users have direct access to GPU device nodes or can invoke GPU system calls without sandboxing.

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 25.1
Interim mitigation

Apply vendor-supplied GPU driver and kernel patches addressing improper input validation in GPU system call paths; restrict GPU access through sandboxing or resource limits for untrusted processes until patches are applied.

Recommended fix Moderate confidence

Imagination Technologies DDK version > 25.1 (contact Imagination Technologies or your GPU hardware vendor for the exact fixed release)

  1. Identify the current DDK (Device Driver Kit) version installed using: cat /sys/class/drm/card0/device/driver_version or checking the-imagination-tech-driver package version
  2. Download the latest Imagination Technologies PowerVR GPU driver package from the official Imagination Technologies developer portal or your GPU hardware vendor
  3. Ensure any running GPU applications are closed before updating
  4. Install the updated driver package using your system's package manager or the provided installer (e.g., sudo apt-get update && sudo apt-get install <new-driver-package> for Linux systems)
  5. Reboot the system to load the new kernel module
  6. Verify the new driver version is loaded successfully: lsmod | grep <imgtec_driver_module> and check dmesg for any loading errors
  7. Test GPU functionality with appropriate tooling to confirm the NULL pointer dereference issue is resolved
Caveat Driver updates may require kernel version compatibility verification; ensure your Linux kernel version is supported by the new driver release before upgrading

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

Fix this in Ddk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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