CVE-2025-68244
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 |
|---|---|---|
| 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 involves a lock inversion issue in the Linux kernel's i915 graphics driver when pinning a virtual memory area (VMA) to the Global Graphics Translation Table (GGTT) address space on certain Intel processors (Cherry View family or Broxton generation SoC with VTD enabled). The problem occurs because a synchronous call to dma_fence_work_commit() leads to a circular locking dependency between reservation_ww and cpu_hotplug locks, which can cause warnings and potential deadlocks in the kernel.
How can this vulnerability impact me? :
This vulnerability can lead to lock inversion and circular locking dependencies in the kernel, potentially causing kernel warnings and deadlocks. This may result in system instability or crashes when the affected graphics driver operations are performed on the specified hardware platforms.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for warnings about circular locking dependencies related to the i915 module, specifically messages like 'WARNING: possible circular locking dependency detected' involving cpu_hotplug_lock and reservation_ww_class_mutex. You can check the kernel log using the command: dmesg | grep -i 'circular locking dependency' or dmesg | grep -i i915.
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 in the kernel code related to drm/i915. Until an update is applied, monitoring for the warning messages and avoiding workloads that trigger the lock inversion on affected hardware (Cherry View processors or Broxton SoCs with VTD enabled) may reduce risk.