drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ea13e5abf807ea912ce84eef6a1946b9a38c6508 · < 0453825167ecc816ec15c736e52316f69db0deb9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()
Nouveau is mostly designed in a way that it's expected that fences only ever get signaled through nouveau_fence_signal(). However, in at least one other place, nouveau_fence_done(), can signal fences, too. If that happens (race) a signaled fence remains in the pending list for a while, until it gets removed by nouveau_fence_update().
Should nouveau_fence_context_kill() run in the meantime, this would be a bug because the function would attempt to set an error code on an already signaled fence.
Have nouveau_fence_context_kill() check for a fence being signaled.
From the CVE record · Linux
A race in the Linux kernel’s Nouveau driver can leave a signaled fence on the pending list, causing a warning if nouveau_fence_context_kill() runs before the fence is removed. The input does not establish an attacker-controlled trigger or specify network access, authentication, or user interaction requirements.
Teams running Linux kernels with the Nouveau driver should check their deployments; affected versions are not specified.