<?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 15:09:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38596 — drm/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38596</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/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code&lt;/p&gt;
&lt;p&gt;The object is potentially already gone after the drm_gem_object_put().
In general the object should be fully constructed before calling
drm_gem_handle_create(), except the debugfs tracking uses a separate
lock and list and separate flag to denotate whether the object is
actually initialized.&lt;/p&gt;
&lt;p&gt;Since I&amp;#39;m touching this all anyway simplify this by only adding the
object to the debugfs when it&amp;#39;s ready for that, which allows us to
delete that separate flag. panthor_gem_debugfs_bo_rm() already checks
whether we&amp;#39;ve actually been added to the list or this is some error
path cleanup.&lt;/p&gt;
&lt;p&gt;v2: Fix build issues for !CONFIG_DEBUGFS (Adrián)&lt;/p&gt;
&lt;p&gt;v3: Add linebreak and remove outdated comment (Liviu)&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/panthor: Fix UAF in panthor_gem_create_with_handle() debugfs code&lt;/p&gt;
&lt;p&gt;The object is potentially already gone after the drm_gem_object_put().
In general the object should be fully constructed before calling
drm_gem_handle_create(), except the debugfs tracking uses a separate
lock and list and separate flag to denotate whether the object is
actually initialized.&lt;/p&gt;
&lt;p&gt;Since I&amp;#39;m touching this all anyway simplify this by only adding the
object to the debugfs when it&amp;#39;s ready for that, which allows us to
delete that separate flag. panthor_gem_debugfs_bo_rm() already checks
whether we&amp;#39;ve actually been added to the list or this is some error
path cleanup.&lt;/p&gt;
&lt;p&gt;v2: Fix build issues for !CONFIG_DEBUGFS (Adrián)&lt;/p&gt;
&lt;p&gt;v3: Add linebreak and remove outdated comment (Liviu)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38596</guid>
    </item>
  </channel>
</rss>
