CVE-2025-21849: drm/i915/gt: Use spin_lock_irqsave() in interruptible context
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/gt: Use spinlockirqsave() in interruptible context
spinlock/unlock() functions used in interrupt contexts could result in a deadlock, as seen in GitLab issue #13399, which occurs when interrupt comes in while holding a lock.
Try to remedy the problem by saving irq state before spin lock acquisition.
v2: add irqs' state save/restore calls to all locks/unlocks in signalirqwork() execution (Maciej)
v3: use with spinlockirqsave() in guclrcdescunpin() instead of other lock/unlock calls and add Fixes and Cc tags (Tvrtko); change title and commit message
(cherry picked from commit c088387ddd6482b40f21ccf23db1125e8fa4af7e)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch c088387ddd6482b40f21ccf23db1125e8fa4af7e
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21849?
CVE-2025-21849 has been classified as a medium-severity vulnerability due to the potential for deadlock in specific interrupt contexts.
How do I fix CVE-2025-21849?
To fix CVE-2025-21849, update the Linux Kernel to a version that includes the patch resolving the misuse of spin_lock_irqsave() in interruptible contexts.
What systems are affected by CVE-2025-21849?
CVE-2025-21849 affects the Linux Kernel, particularly versions using the drm/i915/gt subsystem.
What are the implications of CVE-2025-21849?
CVE-2025-21849 can lead to system deadlocks, potentially causing denial of service under specific conditions.
Is there a workaround for CVE-2025-21849?
While the recommended action is to upgrade the kernel, reducing the use of interrupt contexts could mitigate some immediate risks of CVE-2025-21849.