<?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>Wed, 30 Sep 2026 03:40:30 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72311 — drm/xe: free madvise VMA array on L2 flush failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72311</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: free madvise VMA array on L2 flush failure&lt;/p&gt;
&lt;p&gt;xe_vm_madvise_ioctl() allocates madvise_range.vmas in get_vmas().
After get_vmas() succeeds with at least one VMA, error paths must go
through free_vmas so the array is released before the madvise details are
destroyed.&lt;/p&gt;
&lt;p&gt;The L2 flush validation path added for PAT madvise rejects some
SVM/userptr ranges after get_vmas() has succeeded, but jumps directly to
madv_fini. This skips kfree(madvise_range.vmas), leaking the VMA array on
each failed ioctl.&lt;/p&gt;
&lt;p&gt;Jump to free_vmas instead, matching the other validation failure paths
after get_vmas() has succeeded.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c3a1c3579b1250060da73507a4acef712974c78a)&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: free madvise VMA array on L2 flush failure&lt;/p&gt;
&lt;p&gt;xe_vm_madvise_ioctl() allocates madvise_range.vmas in get_vmas().
After get_vmas() succeeds with at least one VMA, error paths must go
through free_vmas so the array is released before the madvise details are
destroyed.&lt;/p&gt;
&lt;p&gt;The L2 flush validation path added for PAT madvise rejects some
SVM/userptr ranges after get_vmas() has succeeded, but jumps directly to
madv_fini. This skips kfree(madvise_range.vmas), leaking the VMA array on
each failed ioctl.&lt;/p&gt;
&lt;p&gt;Jump to free_vmas instead, matching the other validation failure paths
after get_vmas() has succeeded.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit c3a1c3579b1250060da73507a4acef712974c78a)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72311</guid>
    </item>
  </channel>
</rss>
