<?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 10:45:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72358 — drm/xe/pt: prevent invalid cursor access for purged BOs</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72358</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/pt: prevent invalid cursor access for purged BOs&lt;/p&gt;
&lt;p&gt;During a page table walk for binding, xe_pt_stage_bind() explicitly
skips initializing the xe_res_cursor for purged BOs, treating them
similarly to NULL VMAs by only setting the cursor size.&lt;/p&gt;
&lt;p&gt;However, xe_pt_hugepte_possible() and xe_pt_scan_64K() did not check
if the BO was purged before attempting to walk the cursor using
xe_res_dma() and xe_res_next(). Because the cursor was left
uninitialized for purged BOs, this falls through and triggers
warnings like:&lt;/p&gt;
&lt;p&gt;WARNING: drivers/gpu/drm/xe/xe_res_cursor.h:274 at xe_res_next&lt;/p&gt;
&lt;p&gt;Fix this by explicitly checking if the BO is purged in both
xe_pt_hugepte_possible() and xe_pt_scan_64K(), returning early just
as we do for NULL VMAs, avoiding the invalid cursor accesses entirely.&lt;/p&gt;
&lt;p&gt;As a precaution, also zero-initialize the cursor in xe_pt_stage_bind()
to ensure we don&amp;#39;t pass garbage data into the page table walkers
if we ever hit a similar edge case in the future.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 4c7b9c6ece32440e5a435a92076d049450cd2d2e)&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/pt: prevent invalid cursor access for purged BOs&lt;/p&gt;
&lt;p&gt;During a page table walk for binding, xe_pt_stage_bind() explicitly
skips initializing the xe_res_cursor for purged BOs, treating them
similarly to NULL VMAs by only setting the cursor size.&lt;/p&gt;
&lt;p&gt;However, xe_pt_hugepte_possible() and xe_pt_scan_64K() did not check
if the BO was purged before attempting to walk the cursor using
xe_res_dma() and xe_res_next(). Because the cursor was left
uninitialized for purged BOs, this falls through and triggers
warnings like:&lt;/p&gt;
&lt;p&gt;WARNING: drivers/gpu/drm/xe/xe_res_cursor.h:274 at xe_res_next&lt;/p&gt;
&lt;p&gt;Fix this by explicitly checking if the BO is purged in both
xe_pt_hugepte_possible() and xe_pt_scan_64K(), returning early just
as we do for NULL VMAs, avoiding the invalid cursor accesses entirely.&lt;/p&gt;
&lt;p&gt;As a precaution, also zero-initialize the cursor in xe_pt_stage_bind()
to ensure we don&amp;#39;t pass garbage data into the page table walkers
if we ever hit a similar edge case in the future.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 4c7b9c6ece32440e5a435a92076d049450cd2d2e)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72358</guid>
    </item>
  </channel>
</rss>
