CVE-2025-38371
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-12-16
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.18 (inc) to 5.4.296 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.240 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.187 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.144 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.97 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.37 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.15.6 (exc) |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| debian | debian_linux | 11.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's drm/v3d driver where interrupts are not disabled before resetting the GPU. As a result, an interrupt can be triggered during the GPU reset process, which may cause the GPU to hang and lead to a NULL pointer dereference in an interrupt context. This can cause kernel crashes and system instability.
How can this vulnerability impact me? :
The vulnerability can cause the system to experience GPU hangs and kernel panics due to NULL pointer dereferences during interrupt handling. This can lead to system crashes, instability, and potential denial of service, affecting the reliability and availability of the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel NULL pointer dereference errors related to the v3d driver and GPU resets. Specifically, look for kernel panic messages and error traces similar to the provided example, which include lines like 'Unable to handle kernel NULL pointer dereference at virtual address 00000000000000c0' and references to 'v3d_irq'. You can use commands such as 'dmesg | grep -i v3d' or 'journalctl -k | grep -i v3d' to search for these error messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this vulnerability is resolved, as the issue is fixed by disabling interrupts before resetting the GPU in the drm/v3d driver. Until an update is applied, avoid operations that trigger GPU resets or interrupts related to the v3d driver to reduce the risk of kernel hangs or crashes.