<?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>Mon, 09 Nov 2026 18:09:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98510 — drm/xe/vm: nuke PTs only after unlinking contested VMAs</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98510</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/xe/vm: nuke PTs only after unlinking contested VMAs&lt;/p&gt;
&lt;p&gt;In xe_vm_close_and_put(), external-BO VMAs are queued on the contested
list for deferred destruction via xe_vma_destroy_unlocked(). However,
xe_vm_pt_destroy() was previously invoked before processing contested
VMAs, destroying vm-&amp;gt;pt_root while those VMAs were still linked to their
respective buffer objects (vm_bo-&amp;gt;list.gpuva).&lt;/p&gt;
&lt;p&gt;If a concurrent thread evicts one of those shared buffer objects,
xe_bo_trigger_rebind() holding only bo-&amp;gt;resv walks the BO&amp;#39;s VMAs and, in
fault mode, calls xe_vm_invalidate_vma() -&amp;gt; xe_pt_zap_ptes(). Because
vm-&amp;gt;pt_root[tile-&amp;gt;id] is already NULL, dereferencing pt-&amp;gt;level causes a
NULL ptr deref.&lt;/p&gt;
&lt;p&gt;Fix this by deferring xe_vm_free_scratch() and xe_vm_pt_destroy() until
after all contested VMAs have been unlinked and destroyed.&lt;/p&gt;
&lt;p&gt;User is reporting hitting a NULL ptr deref in xe_pt_zap_ptes(), which
could be explained by this race.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c2863648959489767f08892fd6e90577d2ea0b6a)&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/xe/vm: nuke PTs only after unlinking contested VMAs&lt;/p&gt;
&lt;p&gt;In xe_vm_close_and_put(), external-BO VMAs are queued on the contested
list for deferred destruction via xe_vma_destroy_unlocked(). However,
xe_vm_pt_destroy() was previously invoked before processing contested
VMAs, destroying vm-&amp;gt;pt_root while those VMAs were still linked to their
respective buffer objects (vm_bo-&amp;gt;list.gpuva).&lt;/p&gt;
&lt;p&gt;If a concurrent thread evicts one of those shared buffer objects,
xe_bo_trigger_rebind() holding only bo-&amp;gt;resv walks the BO&amp;#39;s VMAs and, in
fault mode, calls xe_vm_invalidate_vma() -&amp;gt; xe_pt_zap_ptes(). Because
vm-&amp;gt;pt_root[tile-&amp;gt;id] is already NULL, dereferencing pt-&amp;gt;level causes a
NULL ptr deref.&lt;/p&gt;
&lt;p&gt;Fix this by deferring xe_vm_free_scratch() and xe_vm_pt_destroy() until
after all contested VMAs have been unlinked and destroyed.&lt;/p&gt;
&lt;p&gt;User is reporting hitting a NULL ptr deref in xe_pt_zap_ptes(), which
could be explained by this race.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c2863648959489767f08892fd6e90577d2ea0b6a)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98510</guid>
    </item>
  </channel>
</rss>
