<?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://db.gcve.eu</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, 20 Nov 2026 21:30:36 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99772</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99772</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()&lt;/p&gt;
&lt;p&gt;Since commit 541c8f2468b9 (&amp;#34;dma-buf: detach fence ops on signal v3&amp;#34;),
I&amp;#39;m seeing the BUG_ON() triggering in drm_crtc&amp;#39;s fence_to_crtc() via
drm_crtc_fence_get_driver_name() regularly:&lt;/p&gt;
&lt;p&gt;Call trace:
     panic+0x58/0x5c
     die+0x160/0x178
     bug_brk_handler+0x70/0xa4
     call_el1_break_hook+0x3c/0x1a0
     do_el1_brk64+0x24/0x74
     el1_brk64+0x34/0x54
     el1h_64_sync_handler+0x80/0xfc
     el1h_64_sync+0x84/0x88
     drm_crtc_fence_get_driver_name+0x60/0x68 (P)
     sync_file_get_name+0x184/0x45c
     sync_file_ioctl+0x404/0xf70
     __arm64_sys_ioctl+0x124/0x1dc&lt;/p&gt;
&lt;p&gt;This looks to be caused by a code flow similar to the following:&lt;/p&gt;
&lt;p&gt;+++ snip +++
thread A                             thread B&lt;/p&gt;
&lt;p&gt;ioctl(SYNC_IOC_FILE_INFO)
                                     sync_file_ioctl()
                                     sync_file_get_name()
dma_fence_signal_timestamp_locked()  dma_fence_driver_name()
                                       ops = rcu_dereference(fence-&amp;gt;ops)
                                       if (!dma_fence_test_signaled_flag())
                                         ops-&amp;gt;get_driver_name(fence) i.e.
                                         drm_crtc_fence_get_driver_name()
test_and_set_bit(SIGNALED)
RCU_INIT_POINTER(fence-&amp;gt;ops, NULL)
                                     drm_crtc_fence_get_…&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/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()&lt;/p&gt;
&lt;p&gt;Since commit 541c8f2468b9 (&amp;#34;dma-buf: detach fence ops on signal v3&amp;#34;),
I&amp;#39;m seeing the BUG_ON() triggering in drm_crtc&amp;#39;s fence_to_crtc() via
drm_crtc_fence_get_driver_name() regularly:&lt;/p&gt;
&lt;p&gt;Call trace:
     panic+0x58/0x5c
     die+0x160/0x178
     bug_brk_handler+0x70/0xa4
     call_el1_break_hook+0x3c/0x1a0
     do_el1_brk64+0x24/0x74
     el1_brk64+0x34/0x54
     el1h_64_sync_handler+0x80/0xfc
     el1h_64_sync+0x84/0x88
     drm_crtc_fence_get_driver_name+0x60/0x68 (P)
     sync_file_get_name+0x184/0x45c
     sync_file_ioctl+0x404/0xf70
     __arm64_sys_ioctl+0x124/0x1dc&lt;/p&gt;
&lt;p&gt;This looks to be caused by a code flow similar to the following:&lt;/p&gt;
&lt;p&gt;+++ snip +++
thread A                             thread B&lt;/p&gt;
&lt;p&gt;ioctl(SYNC_IOC_FILE_INFO)
                                     sync_file_ioctl()
                                     sync_file_get_name()
dma_fence_signal_timestamp_locked()  dma_fence_driver_name()
                                       ops = rcu_dereference(fence-&amp;gt;ops)
                                       if (!dma_fence_test_signaled_flag())
                                         ops-&amp;gt;get_driver_name(fence) i.e.
                                         drm_crtc_fence_get_driver_name()
test_and_set_bit(SIGNALED)
RCU_INIT_POINTER(fence-&amp;gt;ops, NULL)
                                     drm_crtc_fence_get_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99772</guid>
    </item>
    <item>
      <title>GHSA-m8pm-862w-46pw</title>
      <link>https://db.gcve.eu/vuln/ghsa-m8pm-862w-46pw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()&lt;/p&gt;
&lt;p&gt;Since commit 541c8f2468b9 (&amp;#34;dma-buf: detach fence ops on signal v3&amp;#34;),
I&amp;#39;m seeing the BUG_ON() triggering in drm_crtc&amp;#39;s fence_to_crtc() via
drm_crtc_fence_get_driver_name() regularly:&lt;/p&gt;
&lt;p&gt;Call trace:
     panic+0x58/0x5c
     die+0x160/0x178
     bug_brk_handler+0x70/0xa4
     call_el1_break_hook+0x3c/0x1a0
     do_el1_brk64+0x24/0x74
     el1_brk64+0x34/0x54
     el1h_64_sync_handler+0x80/0xfc
     el1h_64_sync+0x84/0x88
     drm_crtc_fence_get_driver_name+0x60/0x68 (P)
     sync_file_get_name+0x184/0x45c
     sync_file_ioctl+0x404/0xf70
     __arm64_sys_ioctl+0x124/0x1dc&lt;/p&gt;
&lt;p&gt;This looks to be caused by a code flow similar to the following:&lt;/p&gt;
&lt;p&gt;+++ snip +++
thread A                             thread B&lt;/p&gt;
&lt;p&gt;ioctl(SYNC_IOC_FILE_INFO)
                                     sync_file_ioctl()
                                     sync_file_get_name()
dma_fence_signal_timestamp_locked()  dma_fence_driver_name()
                                       ops = rcu_dereference(fence-&amp;gt;ops)
                                       if (!dma_fence_test_signaled_flag())
                                         ops-&amp;gt;get_driver_name(fence) i.e.
                                         drm_crtc_fence_get_driver_name()
test_and_set_bit(SIGNALED)
RCU_INIT_POINTER(fence-&amp;gt;ops, NULL)
                                     drm_crtc_fence_get_…&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/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()&lt;/p&gt;
&lt;p&gt;Since commit 541c8f2468b9 (&amp;#34;dma-buf: detach fence ops on signal v3&amp;#34;),
I&amp;#39;m seeing the BUG_ON() triggering in drm_crtc&amp;#39;s fence_to_crtc() via
drm_crtc_fence_get_driver_name() regularly:&lt;/p&gt;
&lt;p&gt;Call trace:
     panic+0x58/0x5c
     die+0x160/0x178
     bug_brk_handler+0x70/0xa4
     call_el1_break_hook+0x3c/0x1a0
     do_el1_brk64+0x24/0x74
     el1_brk64+0x34/0x54
     el1h_64_sync_handler+0x80/0xfc
     el1h_64_sync+0x84/0x88
     drm_crtc_fence_get_driver_name+0x60/0x68 (P)
     sync_file_get_name+0x184/0x45c
     sync_file_ioctl+0x404/0xf70
     __arm64_sys_ioctl+0x124/0x1dc&lt;/p&gt;
&lt;p&gt;This looks to be caused by a code flow similar to the following:&lt;/p&gt;
&lt;p&gt;+++ snip +++
thread A                             thread B&lt;/p&gt;
&lt;p&gt;ioctl(SYNC_IOC_FILE_INFO)
                                     sync_file_ioctl()
                                     sync_file_get_name()
dma_fence_signal_timestamp_locked()  dma_fence_driver_name()
                                       ops = rcu_dereference(fence-&amp;gt;ops)
                                       if (!dma_fence_test_signaled_flag())
                                         ops-&amp;gt;get_driver_name(fence) i.e.
                                         drm_crtc_fence_get_driver_name()
test_and_set_bit(SIGNALED)
RCU_INIT_POINTER(fence-&amp;gt;ops, NULL)
                                     drm_crtc_fence_get_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-m8pm-862w-46pw</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
