Bug 2351621 (CVE-2025-21849) - CVE-2025-21849 kernel: drm/i915/gt: Use spin_lock_irqsave() in interruptible context
Summary: CVE-2025-21849 kernel: drm/i915/gt: Use spin_lock_irqsave() in interruptible ...
Keywords:
Status: NEW
Alias: CVE-2025-21849
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-03-12 12:23 UTC by OSIDB Bzimport
Modified: 2025-03-12 15:11 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-03-12 12:23:59 UTC
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)

Comment 1 Mauro Matteo Cascella 2025-03-12 15:02:31 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025031212-CVE-2025-21849-c95e@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.