<?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 06:34:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89816 — drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-89816</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: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used&lt;/p&gt;
&lt;p&gt;Commit 1c6ceeee6ebb (&amp;#34;drm/atomic: Fix memleak on ERESTARTSYS during
non-blocking commits&amp;#34;) fixed a very similar issue when the event was
allocated by drm_atomic_helper_setup_commit() itself.&lt;/p&gt;
&lt;p&gt;However, if the event is allocated in prepare_signaling(), it will also be
set to NULL in complete_signaling(), which prevents drm_crtc_commit from
being put in __drm_atomic_helper_crtc_destroy_state().&lt;/p&gt;
&lt;p&gt;Dropping the reference when the event is set to NULL at
complete_signaling() fixes the leak.&lt;/p&gt;
&lt;p&gt;The leak can be reproduced by sending a signal to the thread using
DRM_MODE_PAGE_FLIP_EVENT and using a sw_sync fence to cause the atomic
ioctl to block at drm_atomic_helper_wait_for_fences(). It happened both
with amdgpu and vkms.&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: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used&lt;/p&gt;
&lt;p&gt;Commit 1c6ceeee6ebb (&amp;#34;drm/atomic: Fix memleak on ERESTARTSYS during
non-blocking commits&amp;#34;) fixed a very similar issue when the event was
allocated by drm_atomic_helper_setup_commit() itself.&lt;/p&gt;
&lt;p&gt;However, if the event is allocated in prepare_signaling(), it will also be
set to NULL in complete_signaling(), which prevents drm_crtc_commit from
being put in __drm_atomic_helper_crtc_destroy_state().&lt;/p&gt;
&lt;p&gt;Dropping the reference when the event is set to NULL at
complete_signaling() fixes the leak.&lt;/p&gt;
&lt;p&gt;The leak can be reproduced by sending a signal to the thread using
DRM_MODE_PAGE_FLIP_EVENT and using a sw_sync fence to cause the atomic
ioctl to block at drm_atomic_helper_wait_for_fences(). It happened both
with amdgpu and vkms.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-89816</guid>
    </item>
  </channel>
</rss>
