<?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>Thu, 01 Oct 2026 07:35:06 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-89816</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-89816</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-89816</guid>
    </item>
    <item>
      <title>fkie_cve-2026-89816</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-89816</link>
      <description>&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;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/fkie_cve-2026-89816</guid>
    </item>
    <item>
      <title>GHSA-6f96-mhg4-cfw6</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-6f96-mhg4-cfw6</link>
      <description>&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;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/ghsa-6f96-mhg4-cfw6</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-89816 — drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-89816</link>
      <description>msrc_CVE-2026-89816</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-89816</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11880-1 — kernel-devel-7.2.7-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.7-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11880-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89816</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-89816</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used 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. 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(). Dropping the reference when the event is set to NULL at complete_signaling() fixes the leak. 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; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used 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. 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(). Dropping the reference when the event is set to NULL at complete_signaling() fixes the leak. 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/ubuntu-cve-2026-89816</guid>
    </item>
  </channel>
</rss>
