Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.5
CVE-2025-21849: Linux kernel lock may cause system freeze during graphics interrupts
CVE-2025-21849 · published 1 year ago
Summary
The Linux kernel's graphics driver uses a locking method that can get stuck if an interrupt occurs while the lock is held. This can make the system become unresponsive. Updating to a kernel version that saves and restores interrupt state before acquiring the lock resolves the issue.
What to do
- Update linux kernel to version 6.13.5.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | linux | linux_kernel |
>= 6.9, < 6.12.17 >= 6.13, < 6.13.5 6.14 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| Linux | linux | kernel |
>= 6.13.0, < 6.13.5 Fix: upgrade to 6.13.5
|
Original advisory text
drm/i915/gt: Use spin_lock_irqsave() in interruptible context
In the Linux kernel, the following vulnerability has been resolved:
drm/i915/gt: Use spin_lock_irqsave() in interruptible context
spin_lock/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
signal_irq_work() execution (Maciej)
v3: use with spin_lock_irqsave() in guc_lrc_desc_unpin() instead
of other lock/unlock calls and add Fixes and Cc tags (Tvrtko);
change title and commit message
(cherry picked from commit c088387ddd6482b40f21ccf23db1125e8fa4af7e)
drm/i915/gt: Use spin_lock_irqsave() in interruptible context
spin_lock/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
signal_irq_work() execution (Maciej)
v3: use with spin_lock_irqsave() in guc_lrc_desc_unpin() instead
of other lock/unlock calls and add Fixes and Cc tags (Tvrtko);
change title and commit message
(cherry picked from commit c088387ddd6482b40f21ccf23db1125e8fa4af7e)
References
- https://git.kernel.org/stable/c/2bf1f4c129db7a10920655b000f0292f1ee509c2 URL
- https://git.kernel.org/stable/c/47ae46ac5407646420e06b78e0dad331e56a4bb4 URL
- https://git.kernel.org/stable/c/e49477f7f78598295551d486ecc7f020d796432e URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21849... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2025-21849 Vendor Advisory
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git Product
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-667Improper Locking
Timeline
Published12 Mar 2025
Updated3 Nov 2026
First seen7 Mar 2026
Track software like this
Free during beta