<?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://db.gcve.eu</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>Fri, 20 Nov 2026 21:20:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99657 — mm/mmu_notifier: set -&gt;mm only after mmgrab()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99657</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;mm/mmu_notifier: set -&amp;gt;mm only after mmgrab()&lt;/p&gt;
&lt;p&gt;Radeon uses a non-NULL notifier-&amp;gt;mm to decide whether to call
mmu_interval_notifier_remove() when freeing a buffer object.
__mmu_interval_notifier_insert() sets -&amp;gt;mm before validating the range,
so a wrapping userptr range can leave -&amp;gt;mm set after insertion fails.
Cleanup then tries to remove an unregistered notifier for which no mm
reference was acquired.&lt;/p&gt;
&lt;p&gt;Set -&amp;gt;mm only after mmgrab(), once insertion can no longer fail. While
we could fix radeon&amp;#39;s code instead, setting -&amp;gt;mm on success only makes
the code more robust.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: simplify description ]&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;mm/mmu_notifier: set -&amp;gt;mm only after mmgrab()&lt;/p&gt;
&lt;p&gt;Radeon uses a non-NULL notifier-&amp;gt;mm to decide whether to call
mmu_interval_notifier_remove() when freeing a buffer object.
__mmu_interval_notifier_insert() sets -&amp;gt;mm before validating the range,
so a wrapping userptr range can leave -&amp;gt;mm set after insertion fails.
Cleanup then tries to remove an unregistered notifier for which no mm
reference was acquired.&lt;/p&gt;
&lt;p&gt;Set -&amp;gt;mm only after mmgrab(), once insertion can no longer fail. While
we could fix radeon&amp;#39;s code instead, setting -&amp;gt;mm on success only makes
the code more robust.&lt;/p&gt;
&lt;p&gt;Fix generated by an LLM and sent by Chris Mason in private.&lt;/p&gt;
&lt;p&gt;[ david: simplify description ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99657</guid>
    </item>
  </channel>
</rss>
