HIGHCVSS v3.1 7.8Vulnerability

CVE-2026-99773

In the Linux kernel, the following vulnerability has been resolved: drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind In [1], sashiko reported the following issue: === 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. 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(). If userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device hot-unplug: CPU1 (Userspace) sync_file_get_name() ops = rcu_dereference(fence->ops); if (!dma_fence_test_signaled_flag()) // Preempted or delayed here CPU2 (Driver Teardown) Signals the fence (setting fence->ops = NULL) Destroys and frees the CRTC without waiting for an RCU grace period CPU1 (Resumes) ops->get_driver_name(fence) -> drm_crtc_fence_get_driver_name() crtc = fence_to_crtc(fence); // Casts to the freed CRTC return crtc->dev->driver->name; // Use-after-free ... 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() access the freed CRTC structure? === snap === I believe this to be a correct observation and this patch implements the suggestion of waiting for an RCU grace period before proceeding with destruction of the drm_crtc, so that get_driver_name() and get_timeline_name() can still work.

Properties

Severity
HIGH
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Cvss severity
HIGH
Cvss score
7.8
Epss score
0.00157
Retrieved at
2026-11-22T12:32:29+00:00
Last source
FIRST EPSS
Score
7.8
Cvss version
3.1
Cve id
CVE-2026-99773
Cvss vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
First seen by Signal
2026-11-20T07:38:10+00:00
Name
CVE-2026-99773
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published at
2026-11-20T06:18:16.143
Last modified
2026-11-22T11:17:09.797
Epss percentile
0.04837

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99773 (CVSS v3.1 7.8) — Ninja Signal Threat Intelligence | Ninja Signal