CVE-2025-68203
BaseFortify
Publication date: 2025-12-16
Last updated on: 2025-12-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| amdgpu | 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 potential deadlock in the Linux kernel's amdgpu driver caused by inconsistent spinlock usage between interrupt and process contexts. Specifically, the function amdgpu_userq_fence_driver_process() is called from both interrupt context and process context, but the spinlock is acquired differently in these contexts. In interrupt context, the spinlock is acquired without disabling interrupts, leading to an {IN-HARDIRQ-W} state. When the same lock is acquired in process context, interrupts are enabled while holding the lock, causing inconsistent locking and potential deadlock. The fix involves using spin_lock_irqsave() and spin_unlock_irqrestore() to properly manage the interrupt state regardless of the calling context.
How can this vulnerability impact me? :
This vulnerability can cause a deadlock in the Linux kernel's amdgpu driver, potentially leading to system instability or crashes. Such deadlocks can halt GPU-related operations, degrade system performance, or cause the system to become unresponsive, impacting the reliability of systems using affected AMD GPU drivers.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the kernel logs for specific lock warning messages indicating inconsistent spinlock usage. You can check the kernel log for messages like: "inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage." Use the command: dmesg | grep 'inconsistent {IN-HARDIRQ-W}' to find relevant warnings.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to update the Linux kernel to a version that includes the fix for this issue, which uses spin_lock_irqsave()/spin_unlock_irqrestore() to properly manage interrupt state in the amdgpu_userq_fence_driver_process function, preventing the deadlock caused by inconsistent spinlock usage.