<?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>Fri, 02 Oct 2026 15:08:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74312 — vhost/vdpa: validate virtqueue index in mmap and fault paths</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74312</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/vdpa: validate virtqueue index in mmap and fault paths&lt;/p&gt;
&lt;p&gt;vhost_vdpa_mmap() and vhost_vdpa_fault() use vma-&amp;gt;vm_pgoff as a
virtqueue index for get_vq_notification(), but they do not validate
that the index is smaller than v-&amp;gt;nvqs.&lt;/p&gt;
&lt;p&gt;The ioctl path already performs both a bounds check and
array_index_nospec(), but the mmap/fault path only checks that the
index fits in u16. This allows an out-of-range queue index to reach
driver-specific get_vq_notification() callbacks.&lt;/p&gt;
&lt;p&gt;Fix this by extracting a unified vhost_vdpa_get_vq_notification()
helper that validates the queue index against v-&amp;gt;nvqs and applies
array_index_nospec() before calling the driver callback. Both the
mmap and fault paths use this helper, and the bounds checking is
consolidated into a single location.&lt;/p&gt;
&lt;p&gt;From source inspection, the most defensible impact is out-of-bounds
access in the callback path, potentially leading to invalid PFN
remaps and crash/DoS.&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/vdpa: validate virtqueue index in mmap and fault paths&lt;/p&gt;
&lt;p&gt;vhost_vdpa_mmap() and vhost_vdpa_fault() use vma-&amp;gt;vm_pgoff as a
virtqueue index for get_vq_notification(), but they do not validate
that the index is smaller than v-&amp;gt;nvqs.&lt;/p&gt;
&lt;p&gt;The ioctl path already performs both a bounds check and
array_index_nospec(), but the mmap/fault path only checks that the
index fits in u16. This allows an out-of-range queue index to reach
driver-specific get_vq_notification() callbacks.&lt;/p&gt;
&lt;p&gt;Fix this by extracting a unified vhost_vdpa_get_vq_notification()
helper that validates the queue index against v-&amp;gt;nvqs and applies
array_index_nospec() before calling the driver callback. Both the
mmap and fault paths use this helper, and the bounds checking is
consolidated into a single location.&lt;/p&gt;
&lt;p&gt;From source inspection, the most defensible impact is out-of-bounds
access in the callback path, potentially leading to invalid PFN
remaps and crash/DoS.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74312</guid>
    </item>
  </channel>
</rss>
