<?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-29T16:42:28.840430+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-89800</id>
    <title>CVE-2026-89800 — drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE</title>
    <updated>2026-09-29T16:42:29.045383+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/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE</p>
<p>A successful OP_UNMAP_SPARSE marks its region dirty with
nouveau_uvma_region_dirty() and defers the teardown to
nouveau_uvmm_bind_job_cleanup(); it does not remove the region from
uvmm-&gt;region_mt.</p>
<p>If a later op in the job fails, the unwind path never clears reg-&gt;dirty
(set in one place, cleared nowhere) and sets op-&gt;reg = NULL, so cleanup
skips the teardown. The region is left in the tree with dirty set and its
completion never signalled. Later binds over that range then fail
permanently -- -ENOENT or -EINVAL from the dirty checks, or an unkillable
wait_for_completion() in bind_validate_region() -- for the lifetime of
the uvmm.</p>
<p>Clear reg-&gt;dirty when the unwind reverts the sparse unmap, restoring the
region to the state it was found in.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89800"/>
  </entry>
</feed>
