<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-09T18:35:14.076950+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-98518</id>
    <title>CVE-2026-98518 — drm/nouveau/dmem: pin VRAM for the whole registered range</title>
    <updated>2026-11-09T18:35:14.078589+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: pin VRAM for the whole registered range</p>
<p>Commit c32287471077 ("gpu/drm/nouveau: enable THP support for GPU memory
migration") grew the device-private region that
nouveau_dmem_chunk_alloc() registers from DMEM_CHUNK_SIZE to
DMEM_CHUNK_SIZE * NR_CHUNKS, but left the VRAM buffer object backing that
region at DMEM_CHUNK_SIZE.</p>
<p>nouveau_dmem_page_addr() returns chunk-&gt;bo-&gt;offset plus the page's offset
within the registered region, so every page past the first chunk resolves
to VRAM outside the buffer object.</p>
<p>Size the buffer object to the region it backs.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98518"/>
  </entry>
</feed>
