<?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>Mon, 28 Sep 2026 20:48:07 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-48890 — scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-48890</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;scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM&lt;/p&gt;
&lt;p&gt;storvsc_queuecommand() maps the scatter/gather list using scsi_dma_map(),
which in a confidential VM allocates swiotlb bounce buffers. If the I/O
submission fails in storvsc_do_io(), the I/O is typically retried by higher
level code, but the bounce buffer memory is never freed.  The mostly like
cause of I/O submission failure is a full VMBus channel ring buffer, which
is not uncommon under high I/O loads.  Eventually enough bounce buffer
memory leaks that the confidential VM can&amp;#39;t do any I/O. The same problem
can arise in a non-confidential VM with kernel boot parameter
swiotlb=force.&lt;/p&gt;
&lt;p&gt;Fix this by doing scsi_dma_unmap() in the case of an I/O submission
error, which frees the bounce buffer memory.&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;scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM&lt;/p&gt;
&lt;p&gt;storvsc_queuecommand() maps the scatter/gather list using scsi_dma_map(),
which in a confidential VM allocates swiotlb bounce buffers. If the I/O
submission fails in storvsc_do_io(), the I/O is typically retried by higher
level code, but the bounce buffer memory is never freed.  The mostly like
cause of I/O submission failure is a full VMBus channel ring buffer, which
is not uncommon under high I/O loads.  Eventually enough bounce buffer
memory leaks that the confidential VM can&amp;#39;t do any I/O. The same problem
can arise in a non-confidential VM with kernel boot parameter
swiotlb=force.&lt;/p&gt;
&lt;p&gt;Fix this by doing scsi_dma_unmap() in the case of an I/O submission
error, which frees the bounce buffer memory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-48890</guid>
    </item>
  </channel>
</rss>
