CVE-2025-40225
BaseFortify
Publication date: 2025-12-04
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a kernel panic issue in the Linux kernel's Panthor driver related to the handling of partial unmapping of GPU virtual address (VA) regions. When userspace attempts to partially unmap a GPU VA region using the VM_BIND interface, the driver incorrectly assumes only one new drm_gpuva structure is needed. However, partial unmapping can require two new drm_gpuva structures. This mismatch leads to a NULL pointer dereference, causing the kernel to panic and crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic and crash when a partial unmap operation on a GPU virtual address region is performed. This results in system instability and potential downtime, affecting any applications or services relying on GPU operations and potentially leading to data loss or interruption of service.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel panic caused by a NULL pointer dereference in the panthor driver when a partial unmap of a GPU virtual address region is attempted. Detection involves monitoring system logs for kernel panic messages related to the panthor driver, specifically looking for error messages like 'Unable to handle kernel NULL pointer dereference at virtual address 0000000000000078' and call traces involving 'panthor_gpuva_sm_step_remap'. You can check the kernel logs using commands such as 'dmesg | grep panthor' or 'journalctl -k | grep panthor' to identify related kernel panic events.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where this vulnerability is fixed, as the issue is resolved by a commit addressing the kernel panic in the panthor driver. Until an update is applied, avoid performing partial unmap operations on GPU virtual address regions that use the panthor driver to prevent triggering the kernel panic.