CVE-2025-40152
BaseFortify
Publication date: 2025-11-12
Last updated on: 2025-11-12
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | 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 occurs in the Linux kernel's msm DRM driver when the drm_gem_for_each_gpuvm_bo() function is called from lookup_vma(). It accesses drm_gem_obj.gpuva.list, which is not initialized if the drm driver does not support the DRIVER_GEM_GPUVA feature. This leads to a kernel crash (splat) during bootup when the separate_gpu_drm modparam is set to 1. The issue is fixed by enabling the DRIVER_GEM_GPUVA feature for the msm_kms drm driver.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash during system boot when using the msm DRM driver with the separate_gpu_drm modparam enabled. This results in an inability to properly initialize the graphics subsystem, potentially leading to system instability or failure to boot.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for kernel panic or crash logs related to the drm/msm driver, especially messages indicating a kernel paging request failure or memory abort in the drm msm module. You can look for log entries similar to the following using the command: dmesg | grep -i 'msm' or dmesg | grep -i 'drm'. Specifically, look for errors like 'Unable to handle kernel paging request' or 'Internal error: Oops' related to the msm driver. Additionally, monitoring system logs for crashes when the modparam msm.separate_gpu_drm=1 is set can help detect the issue.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability immediately, ensure that the drm driver for msm_kms has the DRIVER_GEM_GPUVA feature enabled. If possible, update the Linux kernel to a version where this vulnerability is fixed. Alternatively, avoid setting the kernel parameter msm.separate_gpu_drm=1 until the fix is applied, as this setting triggers the issue. Monitoring for kernel updates or patches from your Linux distribution and applying them promptly is recommended.