drm/sched: Increment job count before swapping tail spsc queue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 27105db6c63a571b91d01e749d026105a1e63bcf · < e2d6547dc8b9b332f9bc00875197287a6a4db65a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/sched: Increment job count before swapping tail spsc queue
A small race exists between spsc_queue_push and the run-job worker, in which spsc_queue_push may return not-first while the run-job worker has already idled due to the job count being zero. If this race occurs, job scheduling stops, leading to hangs while waiting on the job’s DMA fences.
Seal this race by incrementing the job count before appending to the SPSC queue.
This race was observed on a drm-tip 6.16-rc1 build with the Xe driver in an SVM test case.
From the CVE record · Linux
A race between SPSC queue insertion and the run-job worker can stop job scheduling, causing hangs while waiting on DMA fences. It was observed on a drm-tip 6.16-rc1 build with the Xe driver during an SVM test. The input does not describe an attacker path or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernel builds with the DRM scheduler should check their exposure, particularly if using a drm-tip 6.16-rc1 build with the Xe driver.