All vulnerabilities

Servers and applications

CVE-2026-99773

drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind

Severity
Unrated
Published
20 Nov 2026
Last changed
20 Nov 2026
Added to UpHeron
20 Nov 2026
Fixed in
6.12.118, 6.18.64, 7.3.5
Sources
CVE Program

Description

In the Linux kernel, the following vulnerability has been resolved:

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

From the CVE Program. Shortened; the full text is there.

Affected software

SoftwareAffected versions
Linux kernelServers and applications · cna:linux|linux
  • From 4.10 before 6.12.118
  • From 6.13 before 6.18.64
  • From 6.19 before 7.3.5

About Linux kernel

Unix-like operating system kernel, basis for all Linux operating systems

From Wikidata, CC0 1.0.
GitHub stars
255,726GitHub, 15 Nov 2026
Forks
67,394GitHub, 15 Nov 2026
Developer
Linus TorvaldsWikidata
License
GNU General Public License, version 2.0Wikidata
Written in
CWikidata
First released
25 Aug 1991Wikidata
First published on GitHub
4 Sept 2011GitHub

References

  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-99773