# CVE-2026-99773: drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < dd9a96b2271e28340acf2e3764914fe5f32f6102 (affected, git); ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (affected, git); ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < f8e6f4deb868fd9da3eda95db222609ab1edc18d (affected, git); ≥ 6d6003c4b613c93973e4e870d83f4bed2ad9ac34; < 3be436cbd3d265fe4fcfbb5b650edad7b2108443 (affected, git). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.16% as of 2026-11-21; percentile 4.84%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102 (CNA: Linux)

- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (CNA: Linux)

- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d (CNA: Linux)

- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443 (CNA: Linux)

- https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99773; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99773; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99773; retrieved 2026-11-22; source updated Not reported

Revision: 9c1fe837ade8d771968843b69e2e54a35dc1f690a9ea869be38f6d35bfbab834

Canonical: https://y2.dev/cve/CVE-2026-99773

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.