{"api_version":"1","generated_at":"2026-11-20T07:30:01+00:00","cve":"CVE-2026-99773","urls":{"html":"https://cve.report/CVE-2026-99773","api":"https://cve.report/api/cve/CVE-2026-99773.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99773","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99773"},"summary":{"title":"drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: ensure dma_fence_ops remain valid during device unbind\n\nIn [1], sashiko reported the following issue:\n\n=== snip ===\nLooking at how these fences are managed, drm_crtc_create_fence()\ncreates a dma_fence without taking a reference to the drm_device or\ndrm_crtc. Because the sync_file framework exposes this fence to\nuserspace, the fence can outlive the CRTC.\n\nThe dma_fence contract requires that data accessed by dma_fence_ops\n(like get_driver_name) must remain valid for an RCU grace period after\nthe fence is signaled. However, drm_crtc_cleanup() and the subsequent\nfreeing of the device do not wait for an RCU grace period via\nsynchronize_rcu().\n\nIf userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device\nhot-unplug:\n\nCPU1 (Userspace)\nsync_file_get_name()\n  ops = rcu_dereference(fence->ops);\n  if (!dma_fence_test_signaled_flag())\n    // Preempted or delayed here\n\nCPU2 (Driver Teardown)\nSignals the fence (setting fence->ops = NULL)\nDestroys and frees the CRTC without waiting for an RCU grace period\n\nCPU1 (Resumes)\n  ops->get_driver_name(fence) -> drm_crtc_fence_get_driver_name()\n  crtc = fence_to_crtc(fence); // Casts to the freed CRTC\n  return crtc->dev->driver->name; // Use-after-free\n\n...\n\nDoes the CRTC or DRM device need to be kept alive for the RCU grace\nperiod, or should the fence hold a proper reference to prevent the\nuse-after-free when get_driver_name() and get_timeline_name() access\nthe freed CRTC structure?\n=== snap ===\n\nI believe this to be a correct observation and this patch implements\nthe suggestion of waiting for an RCU grace period before proceeding\nwith destruction of the drm_crtc, so that get_driver_name() and\nget_timeline_name() can still work.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:16","updated_at":"2026-11-20 06:18:16"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443","name":"https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102","name":"https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d","name":"https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc","name":"https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99773","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99773","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 dd9a96b2271e28340acf2e3764914fe5f32f6102 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 07b2d7a3f2b984c20f5f2630a94f43ede387a8dc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 f8e6f4deb868fd9da3eda95db222609ab1edc18d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6d6003c4b613c93973e4e870d83f4bed2ad9ac34 3be436cbd3d265fe4fcfbb5b650edad7b2108443 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.118 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/drm_crtc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"dd9a96b2271e28340acf2e3764914fe5f32f6102","status":"affected","version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","versionType":"git"},{"lessThan":"07b2d7a3f2b984c20f5f2630a94f43ede387a8dc","status":"affected","version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","versionType":"git"},{"lessThan":"f8e6f4deb868fd9da3eda95db222609ab1edc18d","status":"affected","version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","versionType":"git"},{"lessThan":"3be436cbd3d265fe4fcfbb5b650edad7b2108443","status":"affected","version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/drm_crtc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.10"},{"lessThan":"4.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.118","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.118","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"4.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"4.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: ensure dma_fence_ops remain valid during device unbind\n\nIn [1], sashiko reported the following issue:\n\n=== snip ===\nLooking at how these fences are managed, drm_crtc_create_fence()\ncreates a dma_fence without taking a reference to the drm_device or\ndrm_crtc. Because the sync_file framework exposes this fence to\nuserspace, the fence can outlive the CRTC.\n\nThe dma_fence contract requires that data accessed by dma_fence_ops\n(like get_driver_name) must remain valid for an RCU grace period after\nthe fence is signaled. However, drm_crtc_cleanup() and the subsequent\nfreeing of the device do not wait for an RCU grace period via\nsynchronize_rcu().\n\nIf userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device\nhot-unplug:\n\nCPU1 (Userspace)\nsync_file_get_name()\n  ops = rcu_dereference(fence->ops);\n  if (!dma_fence_test_signaled_flag())\n    // Preempted or delayed here\n\nCPU2 (Driver Teardown)\nSignals the fence (setting fence->ops = NULL)\nDestroys and frees the CRTC without waiting for an RCU grace period\n\nCPU1 (Resumes)\n  ops->get_driver_name(fence) -> drm_crtc_fence_get_driver_name()\n  crtc = fence_to_crtc(fence); // Casts to the freed CRTC\n  return crtc->dev->driver->name; // Use-after-free\n\n...\n\nDoes the CRTC or DRM device need to be kept alive for the RCU grace\nperiod, or should the fence hold a proper reference to prevent the\nuse-after-free when get_driver_name() and get_timeline_name() access\nthe freed CRTC structure?\n=== snap ===\n\nI believe this to be a correct observation and this patch implements\nthe suggestion of waiting for an RCU grace period before proceeding\nwith destruction of the drm_crtc, so that get_driver_name() and\nget_timeline_name() can still work."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:37.923Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102"},{"url":"https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc"},{"url":"https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d"},{"url":"https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443"}],"title":"drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99773","datePublished":"2026-11-20T05:51:37.923Z","dateReserved":"2026-09-25T10:25:14.433Z","dateUpdated":"2026-11-20T05:51:37.923Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:16","lastModifiedDate":"2026-11-20 06:18:16","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99773","Ordinal":"1","Title":"drm/drm_crtc: ensure dma_fence_ops remain valid during device un","CVE":"CVE-2026-99773","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99773","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: ensure dma_fence_ops remain valid during device unbind\n\nIn [1], sashiko reported the following issue:\n\n=== snip ===\nLooking at how these fences are managed, drm_crtc_create_fence()\ncreates a dma_fence without taking a reference to the drm_device or\ndrm_crtc. Because the sync_file framework exposes this fence to\nuserspace, the fence can outlive the CRTC.\n\nThe dma_fence contract requires that data accessed by dma_fence_ops\n(like get_driver_name) must remain valid for an RCU grace period after\nthe fence is signaled. However, drm_crtc_cleanup() and the subsequent\nfreeing of the device do not wait for an RCU grace period via\nsynchronize_rcu().\n\nIf userspace calls ioctl(SYNC_IOC_FILE_INFO) concurrently with a device\nhot-unplug:\n\nCPU1 (Userspace)\nsync_file_get_name()\n  ops = rcu_dereference(fence->ops);\n  if (!dma_fence_test_signaled_flag())\n    // Preempted or delayed here\n\nCPU2 (Driver Teardown)\nSignals the fence (setting fence->ops = NULL)\nDestroys and frees the CRTC without waiting for an RCU grace period\n\nCPU1 (Resumes)\n  ops->get_driver_name(fence) -> drm_crtc_fence_get_driver_name()\n  crtc = fence_to_crtc(fence); // Casts to the freed CRTC\n  return crtc->dev->driver->name; // Use-after-free\n\n...\n\nDoes the CRTC or DRM device need to be kept alive for the RCU grace\nperiod, or should the fence hold a proper reference to prevent the\nuse-after-free when get_driver_name() and get_timeline_name() access\nthe freed CRTC structure?\n=== snap ===\n\nI believe this to be a correct observation and this patch implements\nthe suggestion of waiting for an RCU grace period before proceeding\nwith destruction of the drm_crtc, so that get_driver_name() and\nget_timeline_name() can still work.","Type":"Description","Title":"drm/drm_crtc: ensure dma_fence_ops remain valid during device un"}]}}}