{"api_version":"1","generated_at":"2026-11-20T07:30:01+00:00","cve":"CVE-2026-99770","urls":{"html":"https://cve.report/CVE-2026-99770","api":"https://cve.report/api/cve/CVE-2026-99770.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99770","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99770"},"summary":{"title":"drm/vc4: Publish the output fence outside of job_lock","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vc4: Publish the output fence outside of job_lock\n\njob_lock is taken by the V3D interrupt handler, so nesting an IRQ-unsafe\nlock under it creates an inversion. drm_syncobj_replace_fence() takes\ndrm_syncobj::lock, which other paths acquire with interrupts enabled. For\nexample, a thread interrupted while holding it blocks the handler on\njob_lock, and the handler can only make progress once the submit path\nreleases job_lock, which it cannot do while waiting for drm_syncobj::lock.\n\nThis is reported by lockdep:\n\n[  188.139076] ========================================================\n[  188.139086] WARNING: possible irq lock inversion dependency detected\n[  188.139096] 7.3.0-rc3-00067-gc4f3feeaf60f #67 Tainted: G         C\n[  188.139108] --------------------------------------------------------\n[  188.139116] swapper/0/0 just changed the state of lock:\n[  188.139125] ffff0000054f8ff8 (&vc4->job_lock){-...}-{3:3}, at: vc4_irq+0xa8/0x28c [vc4]\n[  188.139234] but this lock took another, HARDIRQ-unsafe lock in the past:\n[  188.139242]  (&syncobj->lock){+.+.}-{3:3}\n[  188.139256] and interrupts could create inverse lock ordering between them.\n[  188.139267] other info that might help us debug this:\n[  188.139275]  Possible interrupt unsafe locking scenario:\n[  188.139284]        CPU0                    CPU1\n[  188.139291]        ----                    ----\n[  188.139299]   lock(&syncobj->lock);\n[  188.139312]                                local_irq_disable();\n[  188.139320]                                lock(&vc4->job_lock);\n[  188.139335]                                lock(&syncobj->lock);\n[  188.139350]   <Interrupt>\n[  188.139358]     lock(&vc4->job_lock);\n[  188.139372] *** DEADLOCK ***\n\nHand the fence over after job_lock is dropped. The job can complete and\ndrop exec->fence in that window, so take a reference first and publish\nthrough the local pointer, as exec may already be gone.","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/54c219a3de9439fa003b45500a7ea3ad5e2eb6a9","name":"https://git.kernel.org/stable/c/54c219a3de9439fa003b45500a7ea3ad5e2eb6a9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/9ee552a42c3905b4547e83173d46413137ec329a","name":"https://git.kernel.org/stable/c/9ee552a42c3905b4547e83173d46413137ec329a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e16cc0843946e998b6dc6c4b41fee8d9e324ccec","name":"https://git.kernel.org/stable/c/e16cc0843946e998b6dc6c4b41fee8d9e324ccec","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ceee27de7b9d8e9771c8ebda48b6836aa2c4466b","name":"https://git.kernel.org/stable/c/ceee27de7b9d8e9771c8ebda48b6836aa2c4466b","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99770","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99770","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e84fcb95e07442edd7ce3b13973523646dbc581a 54c219a3de9439fa003b45500a7ea3ad5e2eb6a9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e84fcb95e07442edd7ce3b13973523646dbc581a ceee27de7b9d8e9771c8ebda48b6836aa2c4466b git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e84fcb95e07442edd7ce3b13973523646dbc581a e16cc0843946e998b6dc6c4b41fee8d9e324ccec git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e84fcb95e07442edd7ce3b13973523646dbc581a 9ee552a42c3905b4547e83173d46413137ec329a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.18 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/vc4/vc4_gem.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"54c219a3de9439fa003b45500a7ea3ad5e2eb6a9","status":"affected","version":"e84fcb95e07442edd7ce3b13973523646dbc581a","versionType":"git"},{"lessThan":"ceee27de7b9d8e9771c8ebda48b6836aa2c4466b","status":"affected","version":"e84fcb95e07442edd7ce3b13973523646dbc581a","versionType":"git"},{"lessThan":"e16cc0843946e998b6dc6c4b41fee8d9e324ccec","status":"affected","version":"e84fcb95e07442edd7ce3b13973523646dbc581a","versionType":"git"},{"lessThan":"9ee552a42c3905b4547e83173d46413137ec329a","status":"affected","version":"e84fcb95e07442edd7ce3b13973523646dbc581a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/vc4/vc4_gem.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.18"},{"lessThan":"4.18","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.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"4.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"4.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"4.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vc4: Publish the output fence outside of job_lock\n\njob_lock is taken by the V3D interrupt handler, so nesting an IRQ-unsafe\nlock under it creates an inversion. drm_syncobj_replace_fence() takes\ndrm_syncobj::lock, which other paths acquire with interrupts enabled. For\nexample, a thread interrupted while holding it blocks the handler on\njob_lock, and the handler can only make progress once the submit path\nreleases job_lock, which it cannot do while waiting for drm_syncobj::lock.\n\nThis is reported by lockdep:\n\n[  188.139076] ========================================================\n[  188.139086] WARNING: possible irq lock inversion dependency detected\n[  188.139096] 7.3.0-rc3-00067-gc4f3feeaf60f #67 Tainted: G         C\n[  188.139108] --------------------------------------------------------\n[  188.139116] swapper/0/0 just changed the state of lock:\n[  188.139125] ffff0000054f8ff8 (&vc4->job_lock){-...}-{3:3}, at: vc4_irq+0xa8/0x28c [vc4]\n[  188.139234] but this lock took another, HARDIRQ-unsafe lock in the past:\n[  188.139242]  (&syncobj->lock){+.+.}-{3:3}\n[  188.139256] and interrupts could create inverse lock ordering between them.\n[  188.139267] other info that might help us debug this:\n[  188.139275]  Possible interrupt unsafe locking scenario:\n[  188.139284]        CPU0                    CPU1\n[  188.139291]        ----                    ----\n[  188.139299]   lock(&syncobj->lock);\n[  188.139312]                                local_irq_disable();\n[  188.139320]                                lock(&vc4->job_lock);\n[  188.139335]                                lock(&syncobj->lock);\n[  188.139350]   <Interrupt>\n[  188.139358]     lock(&vc4->job_lock);\n[  188.139372] *** DEADLOCK ***\n\nHand the fence over after job_lock is dropped. The job can complete and\ndrop exec->fence in that window, so take a reference first and publish\nthrough the local pointer, as exec may already be gone."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:51:35.728Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/54c219a3de9439fa003b45500a7ea3ad5e2eb6a9"},{"url":"https://git.kernel.org/stable/c/ceee27de7b9d8e9771c8ebda48b6836aa2c4466b"},{"url":"https://git.kernel.org/stable/c/e16cc0843946e998b6dc6c4b41fee8d9e324ccec"},{"url":"https://git.kernel.org/stable/c/9ee552a42c3905b4547e83173d46413137ec329a"}],"title":"drm/vc4: Publish the output fence outside of job_lock","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99770","datePublished":"2026-11-20T05:51:35.728Z","dateReserved":"2026-09-25T10:25:14.433Z","dateUpdated":"2026-11-20T05:51:35.728Z","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":"99770","Ordinal":"1","Title":"drm/vc4: Publish the output fence outside of job_lock","CVE":"CVE-2026-99770","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99770","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vc4: Publish the output fence outside of job_lock\n\njob_lock is taken by the V3D interrupt handler, so nesting an IRQ-unsafe\nlock under it creates an inversion. drm_syncobj_replace_fence() takes\ndrm_syncobj::lock, which other paths acquire with interrupts enabled. For\nexample, a thread interrupted while holding it blocks the handler on\njob_lock, and the handler can only make progress once the submit path\nreleases job_lock, which it cannot do while waiting for drm_syncobj::lock.\n\nThis is reported by lockdep:\n\n[  188.139076] ========================================================\n[  188.139086] WARNING: possible irq lock inversion dependency detected\n[  188.139096] 7.3.0-rc3-00067-gc4f3feeaf60f #67 Tainted: G         C\n[  188.139108] --------------------------------------------------------\n[  188.139116] swapper/0/0 just changed the state of lock:\n[  188.139125] ffff0000054f8ff8 (&vc4->job_lock){-...}-{3:3}, at: vc4_irq+0xa8/0x28c [vc4]\n[  188.139234] but this lock took another, HARDIRQ-unsafe lock in the past:\n[  188.139242]  (&syncobj->lock){+.+.}-{3:3}\n[  188.139256] and interrupts could create inverse lock ordering between them.\n[  188.139267] other info that might help us debug this:\n[  188.139275]  Possible interrupt unsafe locking scenario:\n[  188.139284]        CPU0                    CPU1\n[  188.139291]        ----                    ----\n[  188.139299]   lock(&syncobj->lock);\n[  188.139312]                                local_irq_disable();\n[  188.139320]                                lock(&vc4->job_lock);\n[  188.139335]                                lock(&syncobj->lock);\n[  188.139350]   <Interrupt>\n[  188.139358]     lock(&vc4->job_lock);\n[  188.139372] *** DEADLOCK ***\n\nHand the fence over after job_lock is dropped. The job can complete and\ndrop exec->fence in that window, so take a reference first and publish\nthrough the local pointer, as exec may already be gone.","Type":"Description","Title":"drm/vc4: Publish the output fence outside of job_lock"}]}}}