CVE-2026-99773drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind
- —Not scoredno CVSS score yet
- —Exploitation in 30 daysno EPSS score yet
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 56 days later
· 56 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.
- EPSS (exploitation in 30 days)
- Not scored
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 – < dd9a96b2271e28340acf2e3764914fe5f32f6102
- affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 – < 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc
- affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 – < f8e6f4deb868fd9da3eda95db222609ab1edc18d
- affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 – < 3be436cbd3d265fe4fcfbb5b650edad7b2108443
- affected 4.10
- unaffected < 4.10
- unaffected 6.12.118 – ≤ 6.12.*
- unaffected 6.18.64 – ≤ 6.18.*
- unaffected 7.3.5 – ≤ 7.3.*
- unaffected 7.4-rc2 – ≤ *
References
References4
- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102 (opens in a new tab)
- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (opens in a new tab)
- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d (opens in a new tab)
- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99773)Record last updated .