<?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 10:55:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64008 — accel/rocket: fix UAF via dangling GEM handle in create_bo</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64008</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;accel/rocket: fix UAF via dangling GEM handle in create_bo&lt;/p&gt;
&lt;p&gt;rocket_ioctl_create_bo() inserts a GEM handle into the file&amp;#39;s IDR via
drm_gem_handle_create() early on, then performs several operations that
can fail (sgt allocation, drm_mm insert, iommu_map). If any fail after
the handle is live, the error path calls drm_gem_shmem_object_free()
which kfree&amp;#39;s the object without removing the handle from the IDR.&lt;/p&gt;
&lt;p&gt;This leaves a dangling handle pointing to freed slab memory. Any
subsequent ioctl using that handle (PREP_BO, FINI_BO, SUBMIT) calls
drm_gem_object_lookup() and dereferences freed memory (UAF).&lt;/p&gt;
&lt;p&gt;Fix by moving drm_gem_handle_create() to after all fallible operations
succeed, matching the pattern used by panfrost, lima, and etnaviv.&lt;/p&gt;
&lt;p&gt;Also fix drm_mm_insert_node_generic() whose return value was silently
overwritten by iommu_map_sgtable() on the next line. Add the missing
error check.&lt;/p&gt;
&lt;p&gt;[tomeu: Move handle creation to the very end]&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;accel/rocket: fix UAF via dangling GEM handle in create_bo&lt;/p&gt;
&lt;p&gt;rocket_ioctl_create_bo() inserts a GEM handle into the file&amp;#39;s IDR via
drm_gem_handle_create() early on, then performs several operations that
can fail (sgt allocation, drm_mm insert, iommu_map). If any fail after
the handle is live, the error path calls drm_gem_shmem_object_free()
which kfree&amp;#39;s the object without removing the handle from the IDR.&lt;/p&gt;
&lt;p&gt;This leaves a dangling handle pointing to freed slab memory. Any
subsequent ioctl using that handle (PREP_BO, FINI_BO, SUBMIT) calls
drm_gem_object_lookup() and dereferences freed memory (UAF).&lt;/p&gt;
&lt;p&gt;Fix by moving drm_gem_handle_create() to after all fallible operations
succeed, matching the pattern used by panfrost, lima, and etnaviv.&lt;/p&gt;
&lt;p&gt;Also fix drm_mm_insert_node_generic() whose return value was silently
overwritten by iommu_map_sgtable() on the next line. Add the missing
error check.&lt;/p&gt;
&lt;p&gt;[tomeu: Move handle creation to the very end]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64008</guid>
    </item>
  </channel>
</rss>
