CVE-2025-40310
BaseFortify
Publication date: 2025-12-08
Last updated on: 2025-12-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| amd | amdgpu | * |
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 race condition in the Linux kernel's AMD GPU driver, specifically in the function amdgpu_amdkfd_device_fini_sw. The race occurs between this function and an interrupt when certain cleanup operations are happening, which can lead to a kernel panic due to a NULL pointer dereference.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to panic, leading to system crashes and potential denial of service. It affects systems using the AMD GPU driver, potentially causing instability or downtime.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as a kernel panic related to a NULL pointer dereference in the amdgpu driver, specifically involving amdgpu_amdkfd_device_fini_sw and interrupts. Detection can be done by monitoring kernel logs for panic messages or oops reports containing references to amdgpu, kfd, or the specific error messages shown in the kernel panic log (e.g., 'BUG: kernel NULL pointer dereference', 'amdgpu_amdkfd_device_fini_sw', 'kfd: amdgpu'). Commands to check kernel logs include: 'dmesg | grep -i amdgpu', 'journalctl -k | grep -i amdgpu', or 'grep -i amdgpu /var/log/kern.log'. Additionally, monitoring for system crashes or reboots related to GPU activity may indicate the issue.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the Linux kernel to a version where this race condition in amdgpu_amdkfd_device_fini_sw has been resolved. Until an update is applied, consider limiting or disabling workloads that heavily use the amdgpu driver or KFD nodes to reduce the chance of triggering the race condition. Monitoring system stability and avoiding operations that cause frequent device finalization or interrupts related to amdgpu may help reduce risk.