<?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-10-01T03:19:15.276613+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/bell-cve-2026-89804</id>
    <title>Withdrawn: BELL-CVE-2026-89804 — CVE-2026-89804 does not affect BellSoft software</title>
    <updated>2026-10-01T03:19:15.420432+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <strong>Withdrawn by the publisher.</strong>
        </p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bell-cve-2026-89804"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-89804</id>
    <title>fkie_cve-2026-89804</title>
    <updated>2026-10-01T03:19:15.420507+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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/fkie_cve-2026-89804"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-f67x-82w6-7jjx</id>
    <title>GHSA-f67x-82w6-7jjx</title>
    <updated>2026-10-01T03:19:15.420587+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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/ghsa-f67x-82w6-7jjx"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</id>
    <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
    <updated>2026-10-01T03:19:15.420625+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel-devel-7.2.7-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89804</id>
    <title>UBUNTU-CVE-2026-89804</title>
    <updated>2026-10-01T03:19:15.421207+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/dmem: fix mismatched DMA unmap size for large folios 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():   - nouveau_dmem_migrate_to_ram() on the success path, and   - nouveau_dmem_migrate_copy_one() on the copy-error path. 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/ubuntu-cve-2026-89804"/>
  </entry>
</feed>
