<?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 06:55:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89804 — drm/nouveau/dmem: fix mismatched DMA unmap size for large folios</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89804</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;drm/nouveau/dmem: fix mismatched DMA unmap size for large folios&lt;/p&gt;
&lt;p&gt;Device-private THP migration maps migration buffers with page_size()
and records that length in dma_info-&amp;gt;size.  For a compound folio
page_size() is PAGE_SIZE &amp;lt;&amp;lt; order, but two teardown sites still pass a
literal PAGE_SIZE to dma_unmap_page():&lt;/p&gt;
&lt;p&gt;- nouveau_dmem_migrate_to_ram() on the success path, and
  - nouveau_dmem_migrate_copy_one() on the copy-error path.&lt;/p&gt;
&lt;p&gt;For an order &amp;gt; 0 folio this unmaps less than was mapped, leaking the
remainder of the IOMMU/IOVA mapping.  The other unmap sites, in
nouveau_dmem_migrate_chunk() and nouveau_dmem_evict_chunk(), already
use the saved size; use it here too.&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;drm/nouveau/dmem: fix mismatched DMA unmap size for large folios&lt;/p&gt;
&lt;p&gt;Device-private THP migration maps migration buffers with page_size()
and records that length in dma_info-&amp;gt;size.  For a compound folio
page_size() is PAGE_SIZE &amp;lt;&amp;lt; order, but two teardown sites still pass a
literal PAGE_SIZE to dma_unmap_page():&lt;/p&gt;
&lt;p&gt;- nouveau_dmem_migrate_to_ram() on the success path, and
  - nouveau_dmem_migrate_copy_one() on the copy-error path.&lt;/p&gt;
&lt;p&gt;For an order &amp;gt; 0 folio this unmaps less than was mapped, leaking the
remainder of the IOMMU/IOVA mapping.  The other unmap sites, in
nouveau_dmem_migrate_chunk() and nouveau_dmem_evict_chunk(), already
use the saved size; use it here too.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89804</guid>
    </item>
  </channel>
</rss>
