{"id":"CVE-2026-99773","aliases":[],"cve":{"records":[{"id":"CVE-2026-99773","source":"Linux","state":"PUBLISHED","reasons":[],"replacements":[],"disputed":false,"unsupportedWhenAssigned":false,"reserved":"2026-09-25T10:25:14.433Z","published":"2026-11-20T05:51:37.923Z","modified":"2026-11-22T11:10:05.721Z"}],"publishers":[{"name":"Linux","role":"CNA","organizationId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","modified":"2026-11-22T11:10:05.721Z"}],"references":[{"url":"https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102","tags":[],"source":"Linux"},{"url":"https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc","tags":[],"source":"Linux"},{"url":"https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d","tags":[],"source":"Linux"},{"url":"https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443","tags":[],"source":"Linux"}],"weaknesses":[],"applicability":[{"source":"Linux","statements":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.10","versionEndExcluding":"6.12.118"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.10","versionEndExcluding":"6.18.64"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.10","versionEndExcluding":"7.3.5"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"4.10","versionEndExcluding":"7.4-rc2"}]}]}]}],"prioritization":[]},"title":"drm/drm_crtc: ensure dma_fence_ops remain valid during device unbind","titleSource":"Linux","descriptionSource":"Linux","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.","score":7.8,"severity":"high","published":"2026-11-20T05:51:37.923Z","modified":"2026-11-22T11:10:05.721Z","withdrawn":false,"knownExploited":false,"affected":[],"products":[{"vendor":"Linux","name":"Linux","platforms":[],"versions":[{"version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","status":"affected","lessThan":"dd9a96b2271e28340acf2e3764914fe5f32f6102","versionType":"git"},{"version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","status":"affected","lessThan":"07b2d7a3f2b984c20f5f2630a94f43ede387a8dc","versionType":"git"},{"version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","status":"affected","lessThan":"f8e6f4deb868fd9da3eda95db222609ab1edc18d","versionType":"git"},{"version":"6d6003c4b613c93973e4e870d83f4bed2ad9ac34","status":"affected","lessThan":"3be436cbd3d265fe4fcfbb5b650edad7b2108443","versionType":"git"}],"defaultStatus":"unaffected","cpes":[],"source":"Linux","url":"https://www.cve.org/CVERecord?id=CVE-2026-99773"},{"vendor":"Linux","name":"Linux","platforms":[],"versions":[{"version":"4.10","status":"affected"},{"version":"0","status":"unaffected","lessThan":"4.10","versionType":"semver"},{"version":"6.12.118","status":"unaffected","lessThanOrEqual":"6.12.*","versionType":"semver"},{"version":"6.18.64","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"7.3.5","status":"unaffected","lessThanOrEqual":"7.3.*","versionType":"semver"},{"version":"7.4-rc2","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"defaultStatus":"affected","cpes":[],"source":"Linux","url":"https://www.cve.org/CVERecord?id=CVE-2026-99773"}],"remediation":[],"references":["https://git.kernel.org/stable/c/dd9a96b2271e28340acf2e3764914fe5f32f6102","https://git.kernel.org/stable/c/07b2d7a3f2b984c20f5f2630a94f43ede387a8dc","https://git.kernel.org/stable/c/f8e6f4deb868fd9da3eda95db222609ab1edc18d","https://git.kernel.org/stable/c/3be436cbd3d265fe4fcfbb5b650edad7b2108443"],"sources":[{"name":"CVE","id":"CVE-2026-99773","modified":"2026-11-22T11:10:05.721Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-99773"}],"assessments":[{"source":"Linux","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","score":7.8}],"sourceAffected":[],"observedAt":"2026-11-22T11:23:54.881Z","kev":{"status":"not-listed","checkedAt":"2026-11-22T12:25:32.613Z"},"coverage":[{"source":"NVD","status":"available","checkedAt":"2026-11-21T05:50:32.281Z","attemptedAt":"2026-11-21T05:50:32.281Z"},{"source":"GHSA","status":"available","checkedAt":"2026-11-21T05:35:32.827Z","attemptedAt":"2026-11-21T05:35:32.827Z"},{"source":"EUVD","status":"available","checkedAt":"2026-11-21T05:15:32.527Z","attemptedAt":"2026-11-21T05:15:32.527Z"},{"source":"EPSS","status":"available","checkedAt":"2026-11-21T05:00:31.072Z","attemptedAt":"2026-11-21T05:00:31.072Z"}],"evidence":[{"source":"FIRST EPSS","id":"CVE-2026-99773","url":"https://www.first.org/epss/","probability":0.00157,"percentile":0.04934,"date":"2026-11-20","checkedAt":"2026-11-21T05:00:31.072Z"},{"source":"ENISA EUVD","id":"EUVD-2026-130890","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-130890","modified":"Nov 20, 2026, 5:51:37 AM","checkedAt":"2026-11-21T05:15:32.527Z"},{"source":"GitHub Advisory Database","id":"GHSA-378q-gq2q-w9vq","url":"https://github.com/advisories/GHSA-378q-gq2q-w9vq","modified":"2026-11-20T06:32:18Z","checkedAt":"2026-11-21T05:35:32.827Z"},{"source":"NVD","id":"CVE-2026-99773","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99773","modified":"2026-11-20T06:18:16.143","checkedAt":"2026-11-21T05:50:32.281Z"}],"aiSummary":null}