<?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 16:44:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74614 — vsock/virtio: read virtqueues under worker locks</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74614</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;vsock/virtio: read virtqueues under worker locks&lt;/p&gt;
&lt;p&gt;Commit bd50c5dc182b (&amp;#34;vsock/virtio: add support for device
suspend/resume&amp;#34;) made the *_run flags transition from false to true when
restore installs replacement virtqueues.  The RX, TX and event workers
read their virtqueue before locking and checking the corresponding flag,
so a worker delayed across freeze and restore can observe the replacement
queue&amp;#39;s running state while retaining a pointer to the deleted queue.&lt;/p&gt;
&lt;p&gt;Read each virtqueue under its mutex after checking the run flag, keeping
the pointer and state in the same queue generation.&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;vsock/virtio: read virtqueues under worker locks&lt;/p&gt;
&lt;p&gt;Commit bd50c5dc182b (&amp;#34;vsock/virtio: add support for device
suspend/resume&amp;#34;) made the *_run flags transition from false to true when
restore installs replacement virtqueues.  The RX, TX and event workers
read their virtqueue before locking and checking the corresponding flag,
so a worker delayed across freeze and restore can observe the replacement
queue&amp;#39;s running state while retaining a pointer to the deleted queue.&lt;/p&gt;
&lt;p&gt;Read each virtqueue under its mutex after checking the run flag, keeping
the pointer and state in the same queue generation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74614</guid>
    </item>
  </channel>
</rss>
