AZL-115684: CVE-2026-99770 affecting package kernel 6.6.161.1-1
In the Linux kernel, the following vulnerability has been resolved:
drm/vc4: Publish the output fence outside of joblock
joblock is taken by the V3D interrupt handler, so nesting an IRQ-unsafe lock under it creates an inversion. drmsyncobjreplacefence() takes drmsyncobj::lock, which other paths acquire with interrupts enabled. For example, a thread interrupted while holding it blocks the handler on joblock, and the handler can only make progress once the submit path releases joblock, which it cannot do while waiting for drmsyncobj::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->joblock){-...}-{3:3}, at: vc4irq+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] localirqdisable(); [ 188.139320] lock(&vc4->joblock); [ 188.139335] lock(&syncobj->lock); [ 188.139350] <Interrupt> [ 188.139358] lock(&vc4->joblock); [ 188.139372] DEADLOCK
Hand the fence over after joblock 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
In drm/vc4, take a reference to exec->fence, drop job_lock, then publish the output fence; do not publish it while holding job_lock.