<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T03:37:32.491892+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-89804</id>
    <title>CVE-2026-89804 — drm/nouveau/dmem: fix mismatched DMA unmap size for large folios</title>
    <updated>2026-09-29T03:37:32.511845+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/nouveau/dmem: fix mismatched DMA unmap size for large folios</p>
<p>Device-private THP migration maps migration buffers with page_size()
and records that length in dma_info-&gt;size.  For a compound folio
page_size() is PAGE_SIZE &lt;&lt; order, but two teardown sites still pass a
literal PAGE_SIZE to dma_unmap_page():</p>
<p>- nouveau_dmem_migrate_to_ram() on the success path, and
  - nouveau_dmem_migrate_copy_one() on the copy-error path.</p>
<p>For an order &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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89804"/>
  </entry>
</feed>
