<?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:21:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99773 — drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99773</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/drm_crtc: ensure dma_fence_ops remain valid during device unbind&lt;/p&gt;
&lt;p&gt;In [1], sashiko reported the following issue:&lt;/p&gt;
&lt;p&gt;=== snip ===
Looking at how these fences are managed, drm_crtc_create_fence()
creates a dma_fence without taking a reference to the drm_device or
drm_crtc. Because the sync_file framework exposes this fence to
userspace, the fence can outlive the CRTC.&lt;/p&gt;
&lt;p&gt;The dma_fence contract requires that data accessed by dma_fence_ops
(like get_driver_name) must remain valid for an RCU grace period after
the fence is signaled. However, drm_crtc_cleanup() and the subsequent
freeing of the device do not wait for an RCU grace period via
synchronize_rcu().&lt;/p&gt;
&lt;p&gt;If userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device
hot-unplug:&lt;/p&gt;
&lt;p&gt;CPU1 (Userspace)
sync_file_get_name()
  ops = rcu_dereference(fence-&amp;gt;ops);
  if (!dma_fence_test_signaled_flag())
    // Preempted or delayed here&lt;/p&gt;
&lt;p&gt;CPU2 (Driver Teardown)
Signals the fence (setting fence-&amp;gt;ops = NULL)
Destroys and frees the CRTC without waiting for an RCU grace period&lt;/p&gt;
&lt;p&gt;CPU1 (Resumes)
  ops-&amp;gt;get_driver_name(fence) -&amp;gt; drm_crtc_fence_get_driver_name()
  crtc = fence_to_crtc(fence); // Casts to the freed CRTC
  return crtc-&amp;gt;dev-&amp;gt;driver-&amp;gt;name; // Use-after-free&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;Does the CRTC or DRM device need to be kept alive for the RCU grace
period, or should the fence hold a proper reference to prevent the
use-after-free when get_driver_name() and get_timeline_name() acc…&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/drm_crtc: ensure dma_fence_ops remain valid during device unbind&lt;/p&gt;
&lt;p&gt;In [1], sashiko reported the following issue:&lt;/p&gt;
&lt;p&gt;=== snip ===
Looking at how these fences are managed, drm_crtc_create_fence()
creates a dma_fence without taking a reference to the drm_device or
drm_crtc. Because the sync_file framework exposes this fence to
userspace, the fence can outlive the CRTC.&lt;/p&gt;
&lt;p&gt;The dma_fence contract requires that data accessed by dma_fence_ops
(like get_driver_name) must remain valid for an RCU grace period after
the fence is signaled. However, drm_crtc_cleanup() and the subsequent
freeing of the device do not wait for an RCU grace period via
synchronize_rcu().&lt;/p&gt;
&lt;p&gt;If userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device
hot-unplug:&lt;/p&gt;
&lt;p&gt;CPU1 (Userspace)
sync_file_get_name()
  ops = rcu_dereference(fence-&amp;gt;ops);
  if (!dma_fence_test_signaled_flag())
    // Preempted or delayed here&lt;/p&gt;
&lt;p&gt;CPU2 (Driver Teardown)
Signals the fence (setting fence-&amp;gt;ops = NULL)
Destroys and frees the CRTC without waiting for an RCU grace period&lt;/p&gt;
&lt;p&gt;CPU1 (Resumes)
  ops-&amp;gt;get_driver_name(fence) -&amp;gt; drm_crtc_fence_get_driver_name()
  crtc = fence_to_crtc(fence); // Casts to the freed CRTC
  return crtc-&amp;gt;dev-&amp;gt;driver-&amp;gt;name; // Use-after-free&lt;/p&gt;
&lt;p&gt;...&lt;/p&gt;
&lt;p&gt;Does the CRTC or DRM device need to be kept alive for the RCU grace
period, or should the fence hold a proper reference to prevent the
use-after-free when get_driver_name() and get_timeline_name() acc…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99773</guid>
    </item>
  </channel>
</rss>
