<?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 13:30:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93233 — drm/nouveau/dmem: fix callocated underflow on large folio split</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-93233</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/dmem: fix callocated underflow on large folio split&lt;/p&gt;
&lt;p&gt;nouveau_dmem_folio_free() drops chunk-&amp;gt;callocated once per freed folio,
while a large (compound) device-private folio is only counted once when
it is allocated.  When such a folio is split, the mm core invokes
-&amp;gt;folio_split() (nouveau_dmem_folio_split()) once for each new
sub-folio, but the hook only fixes up the sub-folio metadata and leaves
chunk-&amp;gt;callocated unchanged.&lt;/p&gt;
&lt;p&gt;Each resulting sub-folio is later freed separately, so after a split
the single allocation (+1) is met by N frees (-N), leaving
chunk-&amp;gt;callocated short by N-1.  On the first split/free cycle it
underflows: WARN_ON(!chunk-&amp;gt;callocated) fires, the unsigned counter
wraps and never returns to zero, so the chunk can no longer be
reclaimed (nouveau_dmem_fini() also warns on the leaked count).&lt;/p&gt;
&lt;p&gt;Account for the new sub-folio in the split hook, under the same lock as
nouveau_dmem_folio_free(), so the count stays balanced.&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/dmem: fix callocated underflow on large folio split&lt;/p&gt;
&lt;p&gt;nouveau_dmem_folio_free() drops chunk-&amp;gt;callocated once per freed folio,
while a large (compound) device-private folio is only counted once when
it is allocated.  When such a folio is split, the mm core invokes
-&amp;gt;folio_split() (nouveau_dmem_folio_split()) once for each new
sub-folio, but the hook only fixes up the sub-folio metadata and leaves
chunk-&amp;gt;callocated unchanged.&lt;/p&gt;
&lt;p&gt;Each resulting sub-folio is later freed separately, so after a split
the single allocation (+1) is met by N frees (-N), leaving
chunk-&amp;gt;callocated short by N-1.  On the first split/free cycle it
underflows: WARN_ON(!chunk-&amp;gt;callocated) fires, the unsigned counter
wraps and never returns to zero, so the chunk can no longer be
reclaimed (nouveau_dmem_fini() also warns on the leaked count).&lt;/p&gt;
&lt;p&gt;Account for the new sub-folio in the split hook, under the same lock as
nouveau_dmem_folio_free(), so the count stays balanced.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-93233</guid>
    </item>
  </channel>
</rss>
