{"api_version":"1","generated_at":"2026-11-20T07:29:58+00:00","cve":"CVE-2026-99772","urls":{"html":"https://cve.report/CVE-2026-99772","api":"https://cve.report/api/cve/CVE-2026-99772.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99772","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99772"},"summary":{"title":"drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()\n\nSince commit 541c8f2468b9 (\"dma-buf: detach fence ops on signal v3\"),\nI'm seeing the BUG_ON() triggering in drm_crtc's fence_to_crtc() via\ndrm_crtc_fence_get_driver_name() regularly:\n\n    Call trace:\n     panic+0x58/0x5c\n     die+0x160/0x178\n     bug_brk_handler+0x70/0xa4\n     call_el1_break_hook+0x3c/0x1a0\n     do_el1_brk64+0x24/0x74\n     el1_brk64+0x34/0x54\n     el1h_64_sync_handler+0x80/0xfc\n     el1h_64_sync+0x84/0x88\n     drm_crtc_fence_get_driver_name+0x60/0x68 (P)\n     sync_file_get_name+0x184/0x45c\n     sync_file_ioctl+0x404/0xf70\n     __arm64_sys_ioctl+0x124/0x1dc\n\nThis looks to be caused by a code flow similar to the following:\n\n+++ snip +++\nthread A                             thread B\n\n                                     ioctl(SYNC_IOC_FILE_INFO)\n                                     sync_file_ioctl()\n                                     sync_file_get_name()\ndma_fence_signal_timestamp_locked()  dma_fence_driver_name()\n                                       ops = rcu_dereference(fence->ops)\n                                       if (!dma_fence_test_signaled_flag())\n                                         ops->get_driver_name(fence) i.e.\n                                         drm_crtc_fence_get_driver_name()\ntest_and_set_bit(SIGNALED)\nRCU_INIT_POINTER(fence->ops, NULL)\n                                     drm_crtc_fence_get_driver_name()\n                                       BUG_ON(rcu_access_pointer(fence->ops)\n                                              != &drm_crtc_fence_ops)\n+++ snap +++\n\nIn other words, a fence's ops pointer can now change to NULL on signal,\nwhich wasn't the case before the culprit commit and hence the BUG_ON()\ntriggers.\n\nSimply drop the BUG_ON() as it's usage of fence ops is invalid now, and\nbecause using BUG_ON() and friends to take down the system is an\nunacceptable way to handle a failure.\n\nNote that the adjacent drm_crtc_fence_get_timeline_name() has the same\nproblem and is fixed by this patch as well.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:15","updated_at":"2026-11-20 06:18:15"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/84b31b9b294ac2f41fc7720444b9171e62562e6f","name":"https://git.kernel.org/stable/c/84b31b9b294ac2f41fc7720444b9171e62562e6f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/cb104d395da48d965665fefe8502f71b6e7e3733","name":"https://git.kernel.org/stable/c/cb104d395da48d965665fefe8502f71b6e7e3733","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99772","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99772","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 541c8f2468b933acc5d129e84bd264923675a66e 84b31b9b294ac2f41fc7720444b9171e62562e6f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 541c8f2468b933acc5d129e84bd264923675a66e cb104d395da48d965665fefe8502f71b6e7e3733 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 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":"84b31b9b294ac2f41fc7720444b9171e62562e6f","status":"affected","version":"541c8f2468b933acc5d129e84bd264923675a66e","versionType":"git"},{"lessThan":"cb104d395da48d965665fefe8502f71b6e7e3733","status":"affected","version":"541c8f2468b933acc5d129e84bd264923675a66e","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":"7.1"},{"lessThan":"7.1","status":"unaffected","version":"0","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":"7.3.5","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"7.1","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()\n\nSince commit 541c8f2468b9 (\"dma-buf: detach fence ops on signal v3\"),\nI'm seeing the BUG_ON() triggering in drm_crtc's fence_to_crtc() via\ndrm_crtc_fence_get_driver_name() regularly:\n\n    Call trace:\n     panic+0x58/0x5c\n     die+0x160/0x178\n     bug_brk_handler+0x70/0xa4\n     call_el1_break_hook+0x3c/0x1a0\n     do_el1_brk64+0x24/0x74\n     el1_brk64+0x34/0x54\n     el1h_64_sync_handler+0x80/0xfc\n     el1h_64_sync+0x84/0x88\n     drm_crtc_fence_get_driver_name+0x60/0x68 (P)\n     sync_file_get_name+0x184/0x45c\n     sync_file_ioctl+0x404/0xf70\n     __arm64_sys_ioctl+0x124/0x1dc\n\nThis looks to be caused by a code flow similar to the following:\n\n+++ snip +++\nthread A                             thread B\n\n                                     ioctl(SYNC_IOC_FILE_INFO)\n                                     sync_file_ioctl()\n                                     sync_file_get_name()\ndma_fence_signal_timestamp_locked()  dma_fence_driver_name()\n                                       ops = rcu_dereference(fence->ops)\n                                       if (!dma_fence_test_signaled_flag())\n                                         ops->get_driver_name(fence) i.e.\n                                         drm_crtc_fence_get_driver_name()\ntest_and_set_bit(SIGNALED)\nRCU_INIT_POINTER(fence->ops, NULL)\n                                     drm_crtc_fence_get_driver_name()\n                                       BUG_ON(rcu_access_pointer(fence->ops)\n                                              != &drm_crtc_fence_ops)\n+++ snap +++\n\nIn other words, a fence's ops pointer can now change to NULL on signal,\nwhich wasn't the case before the culprit commit and hence the BUG_ON()\ntriggers.\n\nSimply drop the BUG_ON() as it's usage of fence ops is invalid now, and\nbecause using BUG_ON() and friends to take down the system is an\nunacceptable way to handle a failure.\n\nNote that the adjacent drm_crtc_fence_get_timeline_name() has the same\nproblem and is fixed by this patch as well."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:37.186Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/84b31b9b294ac2f41fc7720444b9171e62562e6f"},{"url":"https://git.kernel.org/stable/c/cb104d395da48d965665fefe8502f71b6e7e3733"}],"title":"drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99772","datePublished":"2026-11-20T05:51:37.186Z","dateReserved":"2026-09-25T10:25:14.433Z","dateUpdated":"2026-11-20T05:51:37.186Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:15","lastModifiedDate":"2026-11-20 06:18:15","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99772","Ordinal":"1","Title":"drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_n","CVE":"CVE-2026-99772","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99772","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_name()\n\nSince commit 541c8f2468b9 (\"dma-buf: detach fence ops on signal v3\"),\nI'm seeing the BUG_ON() triggering in drm_crtc's fence_to_crtc() via\ndrm_crtc_fence_get_driver_name() regularly:\n\n    Call trace:\n     panic+0x58/0x5c\n     die+0x160/0x178\n     bug_brk_handler+0x70/0xa4\n     call_el1_break_hook+0x3c/0x1a0\n     do_el1_brk64+0x24/0x74\n     el1_brk64+0x34/0x54\n     el1h_64_sync_handler+0x80/0xfc\n     el1h_64_sync+0x84/0x88\n     drm_crtc_fence_get_driver_name+0x60/0x68 (P)\n     sync_file_get_name+0x184/0x45c\n     sync_file_ioctl+0x404/0xf70\n     __arm64_sys_ioctl+0x124/0x1dc\n\nThis looks to be caused by a code flow similar to the following:\n\n+++ snip +++\nthread A                             thread B\n\n                                     ioctl(SYNC_IOC_FILE_INFO)\n                                     sync_file_ioctl()\n                                     sync_file_get_name()\ndma_fence_signal_timestamp_locked()  dma_fence_driver_name()\n                                       ops = rcu_dereference(fence->ops)\n                                       if (!dma_fence_test_signaled_flag())\n                                         ops->get_driver_name(fence) i.e.\n                                         drm_crtc_fence_get_driver_name()\ntest_and_set_bit(SIGNALED)\nRCU_INIT_POINTER(fence->ops, NULL)\n                                     drm_crtc_fence_get_driver_name()\n                                       BUG_ON(rcu_access_pointer(fence->ops)\n                                              != &drm_crtc_fence_ops)\n+++ snap +++\n\nIn other words, a fence's ops pointer can now change to NULL on signal,\nwhich wasn't the case before the culprit commit and hence the BUG_ON()\ntriggers.\n\nSimply drop the BUG_ON() as it's usage of fence ops is invalid now, and\nbecause using BUG_ON() and friends to take down the system is an\nunacceptable way to handle a failure.\n\nNote that the adjacent drm_crtc_fence_get_timeline_name() has the same\nproblem and is fixed by this patch as well.","Type":"Description","Title":"drm/drm_crtc: fix race with dma_fence_signal() in ::get_driver_n"}]}}}