<?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://cve.radiocsirt.org</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, 06 Oct 2026 10:11:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38074 — vhost-scsi: protect vq-&gt;log_used with vq-&gt;mutex</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-38074</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;vhost-scsi: protect vq-&amp;gt;log_used with vq-&amp;gt;mutex&lt;/p&gt;
&lt;p&gt;The vhost-scsi completion path may access vq-&amp;gt;log_base when vq-&amp;gt;log_used is
already set to false.&lt;/p&gt;
&lt;p&gt;vhost-thread                       QEMU-thread&lt;/p&gt;
&lt;p&gt;vhost_scsi_complete_cmd_work()
-&amp;gt; vhost_add_used()
   -&amp;gt; vhost_add_used_n()
      if (unlikely(vq-&amp;gt;log_used))
                                      QEMU disables vq-&amp;gt;log_used
                                      via VHOST_SET_VRING_ADDR.
                                      mutex_lock(&amp;amp;vq-&amp;gt;mutex);
                                      vq-&amp;gt;log_used = false now!
                                      mutex_unlock(&amp;amp;vq-&amp;gt;mutex);&lt;/p&gt;
&lt;p&gt;QEMU gfree(vq-&amp;gt;log_base)
        log_used()
        -&amp;gt; log_write(vq-&amp;gt;log_base)&lt;/p&gt;
&lt;p&gt;Assuming the VMM is QEMU. The vq-&amp;gt;log_base is from QEMU userpace and can be
reclaimed via gfree(). As a result, this causes invalid memory writes to
QEMU userspace.&lt;/p&gt;
&lt;p&gt;The control queue path has the same issue.&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;vhost-scsi: protect vq-&amp;gt;log_used with vq-&amp;gt;mutex&lt;/p&gt;
&lt;p&gt;The vhost-scsi completion path may access vq-&amp;gt;log_base when vq-&amp;gt;log_used is
already set to false.&lt;/p&gt;
&lt;p&gt;vhost-thread                       QEMU-thread&lt;/p&gt;
&lt;p&gt;vhost_scsi_complete_cmd_work()
-&amp;gt; vhost_add_used()
   -&amp;gt; vhost_add_used_n()
      if (unlikely(vq-&amp;gt;log_used))
                                      QEMU disables vq-&amp;gt;log_used
                                      via VHOST_SET_VRING_ADDR.
                                      mutex_lock(&amp;amp;vq-&amp;gt;mutex);
                                      vq-&amp;gt;log_used = false now!
                                      mutex_unlock(&amp;amp;vq-&amp;gt;mutex);&lt;/p&gt;
&lt;p&gt;QEMU gfree(vq-&amp;gt;log_base)
        log_used()
        -&amp;gt; log_write(vq-&amp;gt;log_base)&lt;/p&gt;
&lt;p&gt;Assuming the VMM is QEMU. The vq-&amp;gt;log_base is from QEMU userpace and can be
reclaimed via gfree(). As a result, this causes invalid memory writes to
QEMU userspace.&lt;/p&gt;
&lt;p&gt;The control queue path has the same issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-38074</guid>
    </item>
  </channel>
</rss>
