<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T23:56:34.610429+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-21849</id>
    <title>CVE-2025-21849 — drm/i915/gt: Use spin_lock_irqsave() in interruptible context</title>
    <updated>2026-10-01T23:56:34.969286+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/i915/gt: Use spin_lock_irqsave() in interruptible context</p>
<p>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.</p>
<p>Try to remedy the problem by saving irq state before spin lock
acquisition.</p>
<p>v2: add irqs' state save/restore calls to all locks/unlocks in
 signal_irq_work() execution (Maciej)</p>
<p>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</p>
<p>(cherry picked from commit c088387ddd6482b40f21ccf23db1125e8fa4af7e)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-21849"/>
  </entry>
</feed>
