<?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 18:10:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89801 — drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89801</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: fix premature region free on failed OP_UNMAP_SPARSE&lt;/p&gt;
&lt;p&gt;In nouveau_uvmm_bind_job_submit()&amp;#39;s OP_UNMAP_SPARSE arm, op-&amp;gt;reg is set
from nouveau_uvma_region_find(), which only looks the region up and takes
no reference; a region&amp;#39;s sole reference is its membership in
uvmm-&amp;gt;region_mt. Two failure paths leave op-&amp;gt;reg set: the -ENOENT check
when the region is busy, and the drm_gpuvm_sm_unmap_ops_create() failure.
The sibling nouveau_uvmm_sm_unmap_prepare() failure just below clears
op-&amp;gt;reg; these two do not.&lt;/p&gt;
&lt;p&gt;unwind_continue steps back one op, so the failing op is skipped by the
unwind loop and its op-&amp;gt;reg stays set. nouveau_uvmm_bind_job_cleanup()
then enters its if (op-&amp;gt;reg) branch and calls nouveau_uvma_region_remove()
and nouveau_uvma_region_put() on it, dropping the tree&amp;#39;s sole reference
and freeing a region this job never created. The comment above the
cleanup loop documents the broken invariant: op-&amp;gt;reg must be NULL on
submit failure.&lt;/p&gt;
&lt;p&gt;This frees a live region on an unrelated failure, reachable single-job
when drm_gpuvm_sm_unmap_ops_create() returns -ENOMEM; if another job owns
the same region, its cleanup then removes and puts the freed region, a
use-after-free. Clear op-&amp;gt;reg on both failure paths.&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: fix premature region free on failed OP_UNMAP_SPARSE&lt;/p&gt;
&lt;p&gt;In nouveau_uvmm_bind_job_submit()&amp;#39;s OP_UNMAP_SPARSE arm, op-&amp;gt;reg is set
from nouveau_uvma_region_find(), which only looks the region up and takes
no reference; a region&amp;#39;s sole reference is its membership in
uvmm-&amp;gt;region_mt. Two failure paths leave op-&amp;gt;reg set: the -ENOENT check
when the region is busy, and the drm_gpuvm_sm_unmap_ops_create() failure.
The sibling nouveau_uvmm_sm_unmap_prepare() failure just below clears
op-&amp;gt;reg; these two do not.&lt;/p&gt;
&lt;p&gt;unwind_continue steps back one op, so the failing op is skipped by the
unwind loop and its op-&amp;gt;reg stays set. nouveau_uvmm_bind_job_cleanup()
then enters its if (op-&amp;gt;reg) branch and calls nouveau_uvma_region_remove()
and nouveau_uvma_region_put() on it, dropping the tree&amp;#39;s sole reference
and freeing a region this job never created. The comment above the
cleanup loop documents the broken invariant: op-&amp;gt;reg must be NULL on
submit failure.&lt;/p&gt;
&lt;p&gt;This frees a live region on an unrelated failure, reachable single-job
when drm_gpuvm_sm_unmap_ops_create() returns -ENOMEM; if another job owns
the same region, its cleanup then removes and puts the freed region, a
use-after-free. Clear op-&amp;gt;reg on both failure paths.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89801</guid>
    </item>
  </channel>
</rss>
