<?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>Fri, 02 Oct 2026 08:55:11 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46224 — drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46224</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: Fix bo leak in xe_dma_buf_init_obj() on allocation failure&lt;/p&gt;
&lt;p&gt;When drm_gpuvm_resv_object_alloc() fails, the pre-allocated storage bo
is not freed. Add xe_bo_free(storage) before returning the error.&lt;/p&gt;
&lt;p&gt;xe_dma_buf_init_obj() calls xe_bo_init_locked(), which frees the bo on
error. Therefore, xe_dma_buf_init_obj() must also free the bo on its own
error paths. Otherwise, since xe_gem_prime_import() cannot distinguish
whether the failure originated from xe_dma_buf_init_obj() or from
xe_bo_init_locked(), it cannot safely decide whether the bo should be
freed.&lt;/p&gt;
&lt;p&gt;Add comments documenting the ownership semantics: on success, ownership
of storage is transferred to the returned drm_gem_object; on failure,
storage is freed before returning.&lt;/p&gt;
&lt;p&gt;v2: Add comments to explain the free logic.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 78a6c5f899f22338bbf48b44fb8950409c5a69b9)&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: Fix bo leak in xe_dma_buf_init_obj() on allocation failure&lt;/p&gt;
&lt;p&gt;When drm_gpuvm_resv_object_alloc() fails, the pre-allocated storage bo
is not freed. Add xe_bo_free(storage) before returning the error.&lt;/p&gt;
&lt;p&gt;xe_dma_buf_init_obj() calls xe_bo_init_locked(), which frees the bo on
error. Therefore, xe_dma_buf_init_obj() must also free the bo on its own
error paths. Otherwise, since xe_gem_prime_import() cannot distinguish
whether the failure originated from xe_dma_buf_init_obj() or from
xe_bo_init_locked(), it cannot safely decide whether the bo should be
freed.&lt;/p&gt;
&lt;p&gt;Add comments documenting the ownership semantics: on success, ownership
of storage is transferred to the returned drm_gem_object; on failure,
storage is freed before returning.&lt;/p&gt;
&lt;p&gt;v2: Add comments to explain the free logic.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 78a6c5f899f22338bbf48b44fb8950409c5a69b9)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46224</guid>
    </item>
  </channel>
</rss>
