<?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>Thu, 01 Oct 2026 23:17:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74313 — vduse: hold vduse_lock across IDR lookup in open path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74313</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;vduse: hold vduse_lock across IDR lookup in open path&lt;/p&gt;
&lt;p&gt;vduse_dev_open() looks up struct vduse_dev through the IDR and then
acquires dev-&amp;gt;lock only after vduse_lock has been dropped.&lt;/p&gt;
&lt;p&gt;This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the
same object from the IDR and free it before the open path locks the
device, leading to a use-after-free.&lt;/p&gt;
&lt;p&gt;Close this race by keeping vduse_lock held until dev-&amp;gt;lock has been
acquired in the open path, matching the lock ordering already used by
the destroy path.&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;vduse: hold vduse_lock across IDR lookup in open path&lt;/p&gt;
&lt;p&gt;vduse_dev_open() looks up struct vduse_dev through the IDR and then
acquires dev-&amp;gt;lock only after vduse_lock has been dropped.&lt;/p&gt;
&lt;p&gt;This leaves a window where a concurrent VDUSE_DESTROY_DEV can remove the
same object from the IDR and free it before the open path locks the
device, leading to a use-after-free.&lt;/p&gt;
&lt;p&gt;Close this race by keeping vduse_lock held until dev-&amp;gt;lock has been
acquired in the open path, matching the lock ordering already used by
the destroy path.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74313</guid>
    </item>
  </channel>
</rss>
