CVE-2026-99770: Linux kernel · drm/vc4: Publish the output fence outside of job_lock
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e16cc0843946e998b6dc6c4b41fee8d9e324ccec : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:18 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e16cc0843946e998b6dc6c4b41fee8d9e324ccec, ceee27de7b9d8e9771c8ebda48b6836aa2c4466b, 54c219a3de9439fa003b45500a7ea3ad5e2eb6a9 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to e16cc0843946e998b6dc6c4b41fee8d9e324ccec, ceee27de7b9d8e9771c8ebda48b6836aa2c4466b, 54c219a3de9439fa003b45500a7ea3ad5e2eb6a9 or 9ee552a42c3905b4547e83173d46413137ec329a.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel source with specific commits addressing the issue. Users should update to a Linux kernel version that includes these fixes (commits e16cc0843946e998b6dc6c4b41fee8d9e324ccec, ceee27de7b9d8e9771c8ebda48b6836aa2c4466b, 54c219a3de9439fa003b45500a7ea3ad5e2eb6a9, 9ee552a42c3905b4547e83173d46413137ec329a).
Description
A deadlock vulnerability was identified and fixed in the Linux kernel's drm/vc4 driver. The issue involved improper locking order between job_lock and drm_syncobj::lock, which could cause an interrupt lock inversion and deadlock scenario. The fix moves the publication of the output fence outside the job_lock to prevent this inversion.
References
- git.kernel.org/stable/c/54c219a3de9439fa003b45500a7ea3ad5e2eb6a9 (opens in a new tab)
- git.kernel.org/stable/c/ceee27de7b9d8e9771c8ebda48b6836aa2c4466b (opens in a new tab)
- git.kernel.org/stable/c/e16cc0843946e998b6dc6c4b41fee8d9e324ccec (opens in a new tab)
- git.kernel.org/stable/c/9ee552a42c3905b4547e83173d46413137ec329a (opens in a new tab)