CVE-2025-40247
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 | 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 NULL pointer dereference error in the Linux kernel's drm/msm driver. It occurs due to an error path cleanup issue where a preallocation cleanup function is called without a preceding successful preallocation allocation. This leads to a crash (kernel oops) when the system tries to handle memory management in the msm_vma_job_free function, triggered by an ioctl call.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a NULL pointer dereference, leading to system instability or denial of service. Since it occurs in the kernel's memory management for the msm driver, it may affect systems using this driver, potentially causing unexpected reboots or service interruptions.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel NULL pointer dereference leading to an 'Oops' error in the Linux kernel logs, specifically related to drm/msm and functions like msm_vma_job_free and build_detached_freelist. Detection involves monitoring kernel logs for such error messages. You can use commands like 'dmesg | grep -i oops' or 'journalctl -k | grep -i drm' to look for relevant kernel error traces indicating this issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves applying the patch that fixes the pgtable prealloc error path in the drm/msm driver. Since this is a kernel vulnerability, updating the Linux kernel to a version that includes the fix (post patch at https://patchwork.freedesktop.org/patch/678677/) is recommended. Until then, avoid triggering the vulnerable ioctl calls related to msm_vma_job_free if possible.