CVE-2025-21849 drm/i915/gt: Use spin_lock_irqsave() in interruptible context

Medium 5.5 Published Updated

A race condition in the Intel i915 graphics driver can cause a deadlock when interrupts occur during lock acquisition, leading to system denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2025-21849?

CVE-2025-21849 is a medium-severity vulnerability in Linux kernel, published on 12 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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)

Weakness: CWE-667

Which versions are affected by CVE-2025-21849?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2025-21849?

Apply the vendor's patch.

Is CVE-2025-21849 being exploited?

There is no known exploitation of CVE-2025-21849 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2025-21849, DEBIAN-CVE-2025-21849, GHSA-g8v7-wpgp-c9xw, UBUNTU-CVE-2025-21849.

Is CVE-2025-21849 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free