<?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 04:55:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38672 — Revert "drm/gem-dma: Use dma_buf from GEM object instance"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38672</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;Revert &amp;#34;drm/gem-dma: Use dma_buf from GEM object instance&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit e8afa1557f4f963c9a511bd2c6074a941c308685.&lt;/p&gt;
&lt;p&gt;The dma_buf field in struct drm_gem_object is not stable over the
object instance&amp;#39;s lifetime. The field becomes NULL when user space
releases the final GEM handle on the buffer object. This resulted
in a NULL-pointer deref.&lt;/p&gt;
&lt;p&gt;Workarounds in commit 5307dce878d4 (&amp;#34;drm/gem: Acquire references on
GEM handles for framebuffers&amp;#34;) and commit f6bfc9afc751 (&amp;#34;drm/framebuffer:
Acquire internal references on GEM handles&amp;#34;) only solved the problem
partially. They especially don&amp;#39;t work for buffer objects without a DRM
framebuffer associated.&lt;/p&gt;
&lt;p&gt;Hence, this revert to going back to using .import_attach-&amp;gt;dmabuf.&lt;/p&gt;
&lt;p&gt;v3:
- cc stable&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;Revert &amp;#34;drm/gem-dma: Use dma_buf from GEM object instance&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit e8afa1557f4f963c9a511bd2c6074a941c308685.&lt;/p&gt;
&lt;p&gt;The dma_buf field in struct drm_gem_object is not stable over the
object instance&amp;#39;s lifetime. The field becomes NULL when user space
releases the final GEM handle on the buffer object. This resulted
in a NULL-pointer deref.&lt;/p&gt;
&lt;p&gt;Workarounds in commit 5307dce878d4 (&amp;#34;drm/gem: Acquire references on
GEM handles for framebuffers&amp;#34;) and commit f6bfc9afc751 (&amp;#34;drm/framebuffer:
Acquire internal references on GEM handles&amp;#34;) only solved the problem
partially. They especially don&amp;#39;t work for buffer objects without a DRM
framebuffer associated.&lt;/p&gt;
&lt;p&gt;Hence, this revert to going back to using .import_attach-&amp;gt;dmabuf.&lt;/p&gt;
&lt;p&gt;v3:
- cc stable&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38672</guid>
    </item>
  </channel>
</rss>
