drm/scheduler: signal scheduled fence when kill job
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/scheduler: signal scheduled fence when kill job
When an entity from application B is killed, drm_sched_entity_kill() removes all jobs belonging to that entity through drm_sched_entity_kill_jobs_work(). If application A's job depends on a scheduled fence from application B's job, and that fence is not properly signaled during the killing process, application A's dependency cannot be cleared.
This leads to application A hanging indefinitely while waiting for a dependency that will never be resolved. Fix this issue by ensuring that scheduled fences are properly signaled when an entity is killed, allowing dependent applications to continue execution.
From the CVE record · Linux
The Linux kernel DRM scheduler may fail to signal a scheduled fence when an application's entity is killed. An attacker who can trigger this condition could leave another application hanging indefinitely if its job depends on that fence. The input does not specify network access, authentication, or user-interaction requirements.
Teams running the Linux kernel should check their deployments; affected versions are not specified.