CVE-2026-99770: drm/vc4: Publish the output fence outside of job_lock

Published Nov 20, 2026
·
Updated

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

7 affected componentsFixes available
linux/kernel>=4.18.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1
  5. Compensating control

    In drm/vc4, take a reference to the output fence before dropping exec->fence, then publish it through a local pointer after releasing job_lock.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

What conditions are required to trigger this issue?

The issue requires VC4/V3D job submission to publish an output fence while holding job_lock, concurrent with an interrupt path that also takes job_lock. A conflicting path must hold drm_syncobj::lock with interrupts enabled, allowing an interrupt-driven lock-order inversion.

2

What is the practical impact?

The lock inversion can deadlock the V3D interrupt handler and the job submission path. The description identifies lockdep warnings as an indicator of the unsafe locking relationship.

3

How can I determine whether a system may be affected?

Systems using the VC4/V3D DRM driver may be affected if they contain the vulnerable locking arrangement. Lockdep may report a possible IRQ lock inversion involving vc4->job_lock and syncobj->lock.

4

What mitigation is available if an update cannot be applied immediately?

The provided information does not identify a configuration workaround. Reducing or avoiding workloads that concurrently submit VC4/V3D jobs and use DRM synchronization objects may reduce exposure, but this is not stated as a complete mitigation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203