CVE-2025-58411
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-01-14
Assigner: imaginationtech
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| imagination_technologies | gpu_driver_development_kit | to 24.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves improper GPU system calls made by software running as a non-privileged user, which cause mismanagement of resource reference counting. This leads to a use-after-free scenario where internal GPU resources are accessed after being freed, potentially causing kernel exceptions, memory corruption, or unauthorized memory access. Essentially, the GPU driver mishandles resource lifetimes, allowing attackers to exploit this flaw to affect system stability or security. [1]
How can this vulnerability impact me? :
The vulnerability can allow an attacker with non-privileged access to cause kernel crashes, arbitrary writes to kernel or physical memory, and potentially gain unauthorized access to sensitive information. This can lead to system instability, denial of service, or escalation of privileges by exploiting the use-after-free condition in the GPU driver. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for improper GPU system calls and unusual GPU firmware behavior, such as kernel exceptions, crashes, or instability. Since the issue arises from improper GPU system calls by non-privileged users or kernel software inside Guest VMs, you can check system logs for GPU-related errors or crashes. Commands to inspect GPU driver logs or kernel messages include: `dmesg | grep -i gpu`, `journalctl -k | grep -i gpu`, and monitoring for unusual GPU firmware crashes or kernel exceptions. Additionally, monitoring for unexpected GPU resource usage or abnormal GPU system call activity may help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Imagination Technologies GPU Driver Development Kit (DDK) firmware and kernel modules to the latest versions that include protections against out-of-bounds accesses, use-after-free conditions, and improper GPU system calls. These updates implement improved error handling, input parameter validation, locking mechanisms, and restrictions on GPU system call usage. Until updates are applied, restrict non-privileged user access to GPU system calls and avoid running untrusted kernel software inside Guest VMs to reduce risk. [1]