<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 21:58:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90291 — module/dups: Fix use-after-free in kmod_dup_req lifetime handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90291</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;module/dups: Fix use-after-free in kmod_dup_req lifetime handling&lt;/p&gt;
&lt;p&gt;The kmod dups code uses RCU to ensure that a kmod_dup_req instance is freed
only after it is no longer referenced. When releasing an instance, the
kmod_dup_request_delete() function removes the kmod_dup_req from the
dup_kmod_reqs list, waits via synchronize_rcu() and finally frees it.
However, this doesn&amp;#39;t work correctly because parallel users referencing the
instance in kmod_dup_request_exists_wait() don&amp;#39;t enter an RCU read-side
critical section. This can result in a use-after-free.&lt;/p&gt;
&lt;p&gt;The kmod_dup_request_exists_wait() function may need to hold a valid
reference to a kmod_dup_req instance across a blocking wait until the
corresponding modprobe command completes. This makes it unsuitable for RCU.&lt;/p&gt;
&lt;p&gt;Fix the issue by changing the lifecycle management of kmod_dup_req to use
reference counting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;module/dups: Fix use-after-free in kmod_dup_req lifetime handling&lt;/p&gt;
&lt;p&gt;The kmod dups code uses RCU to ensure that a kmod_dup_req instance is freed
only after it is no longer referenced. When releasing an instance, the
kmod_dup_request_delete() function removes the kmod_dup_req from the
dup_kmod_reqs list, waits via synchronize_rcu() and finally frees it.
However, this doesn&amp;#39;t work correctly because parallel users referencing the
instance in kmod_dup_request_exists_wait() don&amp;#39;t enter an RCU read-side
critical section. This can result in a use-after-free.&lt;/p&gt;
&lt;p&gt;The kmod_dup_request_exists_wait() function may need to hold a valid
reference to a kmod_dup_req instance across a blocking wait until the
corresponding modprobe command completes. This makes it unsuitable for RCU.&lt;/p&gt;
&lt;p&gt;Fix the issue by changing the lifecycle management of kmod_dup_req to use
reference counting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90291</guid>
    </item>
  </channel>
</rss>
