CVE-2026-99773
Severity unknownNo known exploitationFix availabledrm/drm_crtc: ensure dma_fence_ops remain valid during device unbind
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 5% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 before 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc | 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc | CVE Program |
| Linux | Linux | from 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 before f8e6f4deb868fd9da3eda95db222609ab1edc18d | f8e6f4deb868fd9da3eda95db222609ab1edc18d | CVE Program |
| Linux | Linux | from 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 before 3be436cbd3d265fe4fcfbb5b650edad7b2108443 | 3be436cbd3d265fe4fcfbb5b650edad7b2108443 | CVE Program |
| Linux | Linux | from 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 before dd9a96b2271e28340acf2e3764914fe5f32f6102 | dd9a96b2271e28340acf2e3764914fe5f32f6102 | CVE Program |
| Linux | Linux | 4.10 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 4.10 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (opens in a new tab)
- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443 (opens in a new tab)
- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102 (opens in a new tab)
- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d (opens in a new tab)