CVE-2026-99773
drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < dd9a96b2271e28340acf2e3764914fe5f32f6102 (affected, git) ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (affected, git) ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < f8e6f4deb868fd9da3eda95db222609ab1edc18d (affected, git) ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < 3be436cbd3d265fe4fcfbb5b650edad7b2108443 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.10 (affected) ≥ 0; < 4.10 (unaffected, semver) ≥ 6.12.118; ≤ 6.12.* (unaffected, semver) ≥ 6.18.64; ≤ 6.18.* (unaffected, semver) ≥ 7.3.5; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA: Linux |
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102CNA: Linux
- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dcCNA: Linux
- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18dCNA: Linux
- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443CNA: Linux
- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.