drm/i915/gt: Use spin_lock_irqsave() in interruptible context
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2bf1f4c129db7a10920655b000f0292f1ee509c2, Kernel 47ae46ac5407646420e06b78e0dad331e56a4bb4 and Kernel e49477f7f78598295551d486ecc7f020d796432e.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=2f2cc53b5fe7022f3ae602eb24573d52f8740959 <2bf1f4c129db7a10920655b000f0292f1ee509c2, >=2f2cc53b5fe7022f3ae602eb24573d52f8740959 <47ae46ac5407646420e06b78e0dad331e56a4bb4, >=2f2cc53b5fe7022f3ae602eb24573d52f8740959 <e49477f7f78598295551d486ecc7f020d796432e | 2bf1f4c129db7a10920655b000f0292f1ee509c2, 47ae46ac5407646420e06b78e0dad331e56a4bb4, e49477f7f78598295551d486ecc7f020d796432e |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket