<?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 03:54:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89800 — drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89800</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/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE&lt;/p&gt;
&lt;p&gt;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-&amp;gt;region_mt.&lt;/p&gt;
&lt;p&gt;If a later op in the job fails, the unwind path never clears reg-&amp;gt;dirty
(set in one place, cleared nowhere) and sets op-&amp;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.&lt;/p&gt;
&lt;p&gt;Clear reg-&amp;gt;dirty when the unwind reverts the sparse unmap, restoring the
region to the state it was found in.&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/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE&lt;/p&gt;
&lt;p&gt;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-&amp;gt;region_mt.&lt;/p&gt;
&lt;p&gt;If a later op in the job fails, the unwind path never clears reg-&amp;gt;dirty
(set in one place, cleared nowhere) and sets op-&amp;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.&lt;/p&gt;
&lt;p&gt;Clear reg-&amp;gt;dirty when the unwind reverts the sparse unmap, restoring the
region to the state it was found in.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89800</guid>
    </item>
  </channel>
</rss>
