Answer in brief
CVE-2026-93192 records a Unknown severity vulnerability in drm/v3d: Clear queue->active_job when v3d_fence_create() fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a783a09ee76d6259296dc6aeea2b6884fa526980 <bdeb73d7312100e00c3e643ff233f09b6ec114aa || >=a783a09ee76d6259296dc6aeea2b6884fa526980 <3a8aa74859dd73eaa76c55eb74da708e56ef51c5 || >=a783a09ee76d6259296dc6aeea2b6884fa526980 <0b9878aba5cf93bc2b55ba9eb807757ce3239bec || >=a783a09ee76d6259296dc6aeea2b6884fa526980 <25a1669907512e927fab9ad4d4fb74ff57f63cd9 | bdeb73d7312100e00c3e643ff233f09b6ec114aa, 3a8aa74859dd73eaa76c55eb74da708e56ef51c5, 0b9878aba5cf93bc2b55ba9eb807757ce3239bec, 25a1669907512e927fab9ad4d4fb74ff57f63cd9 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
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.
Quoted source text, attributed separately from HOL analysis.