drm/v3d: Clear queue->active_job when v3d_fence_create() fails
CVE-2026-93192 · published 17 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-93192?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: a783a09ee76d6259296dc6aeea2b6884fa526980 to < 1f661f42beb558b2d21882f0cd527ed6c8e7e749, a783a09ee76d6259296dc6aeea2b6884fa526980 to < bdeb73d7312100e00c3e643ff233f09b6ec114aa, a783a09ee76d6259296dc6aeea2b6884fa526980 to < 3a8aa74859dd73eaa76c55eb74da708e56ef51c5, a783a09ee76d6259296dc6aeea2b6884fa526980 to < 0b9878aba5cf93bc2b55ba9eb807757ce3239bec
- Linux Linux: 5.3
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Clear queue->active_job when v3d_fence_create() fails
The run_job() callbacks for BIN, RENDER, TFU and CSD assign the incoming
job to queue->active_job before calling v3d_fence_create(). If
v3d_fence_create() fails, the callback returns NULL without clearing
active_job, leaving a dangling pointer.
Create a failure path in all run_job() callbacks that clears the active
job before returning NULL. The BIN path takes queue->queue_lock around the
clear as it races against v3d_overflow_mem_work(); RENDER, TFU and CSD
paths have no concurrent reader, so the clear is lock-free.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/1f661f42beb558b2d21882f0cd527ed6c8e7e749
- git.kernel.org/stable/c/bdeb73d7312100e00c3e643ff233f09b6ec114aa
- git.kernel.org/stable/c/3a8aa74859dd73eaa76c55eb74da708e56ef51c5
- git.kernel.org/stable/c/0b9878aba5cf93bc2b55ba9eb807757ce3239bec
- git.kernel.org/stable/c/25a1669907512e927fab9ad4d4fb74ff57f63cd9
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON