<?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-09-29T18:07:03.343344+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-2026-43115</id>
    <title>CVE-2026-43115 — srcu: Use irq_work to start GP in tiny SRCU</title>
    <updated>2026-09-29T18:07:03.344586+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>srcu: Use irq_work to start GP in tiny SRCU</p>
<p>Tiny SRCU's srcu_gp_start_if_needed() directly calls schedule_work(),
which acquires the workqueue pool-&gt;lock.</p>
<p>This causes a lockdep splat when call_srcu() is called with a scheduler
lock held, due to:</p>
<p>call_srcu() [holding pi_lock]
    srcu_gp_start_if_needed()
      schedule_work() -&gt; pool-&gt;lock</p>
<p>workqueue_init() / create_worker() [holding pool-&gt;lock]
    wake_up_process() -&gt; try_to_wake_up() -&gt; pi_lock</p>
<p>Also add irq_work_sync() to cleanup_srcu_struct() to prevent a
use-after-free if a queued irq_work fires after cleanup begins.</p>
<p>Tested with rcutorture SRCU-T and no lockdep warnings.</p>
<p>[ Thanks to Boqun for similar fix in patch "rcu: Use an intermediate irq_work
to start process_srcu()" ]</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-43115"/>
  </entry>
</feed>
