<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-20T21:20:28.146161+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99773</id>
    <title>CVE-2026-99773 — drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind</title>
    <updated>2026-11-20T21:20:28.148366+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind</p>
<p>In [1], sashiko reported the following issue:</p>
<p>=== 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.</p>
<p>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().</p>
<p>If userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device
hot-unplug:</p>
<p>CPU1 (Userspace)
sync_file_get_name()
  ops = rcu_dereference(fence-&gt;ops);
  if (!dma_fence_test_signaled_flag())
    // Preempted or delayed here</p>
<p>CPU2 (Driver Teardown)
Signals the fence (setting fence-&gt;ops = NULL)
Destroys and frees the CRTC without waiting for an RCU grace period</p>
<p>CPU1 (Resumes)
  ops-&gt;get_driver_name(fence) -&gt; drm_crtc_fence_get_driver_name()
  crtc = fence_to_crtc(fence); // Casts to the freed CRTC
  return crtc-&gt;dev-&gt;driver-&gt;name; // Use-after-free</p>
<p>...</p>
<p>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…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99773"/>
  </entry>
</feed>
