drm/vc4: Publish the output fence outside of job_lock
Summary
| CVE | CVE-2026-99770 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-20 06:18:15 UTC |
| Updated | 2026-11-20 06:18:15 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
drm/vc4: Publish the output fence outside of job_lock
job_lock is taken by the V3D interrupt handler, so nesting an IRQ-unsafe
lock under it creates an inversion. drm_syncobj_replace_fence() takes
drm_syncobj::lock, which other paths acquire with interrupts enabled. For
example, a thread interrupted while holding it blocks the handler on
job_lock, and the handler can only make progress once the submit path
releases job_lock, which it cannot do while waiting for drm_syncobj::lock.
This is reported by lockdep:
[ 188.139076] ========================================================
[ 188.139086] WARNING: possible irq lock inversion dependency detected
[ 188.139096] 7.3.0-rc3-00067-gc4f3feeaf60f #67 Tainted: G C
[ 188.139108] --------------------------------------------------------
[ 188.139116] swapper/0/0 just changed the state of lock:
[ 188.139125] ffff0000054f8ff8 (&vc4->job_lock){-...}-{3:3}, at: vc4_irq+0xa8/0x28c [vc4]
[ 188.139234] but this lock took another, HARDIRQ-unsafe lock in the past:
[ 188.139242] (&syncobj->lock){+.+.}-{3:3}
[ 188.139256] and interrupts could create inverse lock ordering between them.
[ 188.139267] other info that might help us debug this:
[ 188.139275] Possible interrupt unsafe locking scenario:
[ 188.139284] CPU0 CPU1
[ 188.139291] ---- ----
[ 188.139299] lock(&syncobj->lock);
[ 188.139312] local_irq_disable();
[ 188.139320] lock(&vc4->job_lock);
[ 188.139335] lock(&syncobj->lock);
[ 188.139350] <Interrupt>
[ 188.139358] lock(&vc4->job_lock);
[ 188.139372] *** DEADLOCK ***
Hand the fence over after job_lock is dropped. The job can complete and
drop exec->fence in that window, so take a reference first and publish
through the local pointer, as exec may already be gone. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected e84fcb95e07442edd7ce3b13973523646dbc581a 54c219a3de9439fa003b45500a7ea3ad5e2eb6a9 git |
Not specified |
| CNA |
Linux |
Linux |
affected e84fcb95e07442edd7ce3b13973523646dbc581a ceee27de7b9d8e9771c8ebda48b6836aa2c4466b git |
Not specified |
| CNA |
Linux |
Linux |
affected e84fcb95e07442edd7ce3b13973523646dbc581a e16cc0843946e998b6dc6c4b41fee8d9e324ccec git |
Not specified |
| CNA |
Linux |
Linux |
affected e84fcb95e07442edd7ce3b13973523646dbc581a 9ee552a42c3905b4547e83173d46413137ec329a git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.18 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.18 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.118 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.64 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3.5 7.3.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.4-rc2 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/54c219a3de9439fa003b45500a7ea3ad5e2eb6a9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9ee552a42c3905b4547e83173d46413137ec329a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e16cc0843946e998b6dc6c4b41fee8d9e324ccec |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/ceee27de7b9d8e9771c8ebda48b6836aa2c4466b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.