drm/vc4: Shut down BO cache timer before teardown
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c826a6e1064419f78855463cf29ce9e8b9d25bf4 · < 6273dd3ffb54ec581855b82ae77331b66028249c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/vc4: Shut down BO cache timer before teardown
The BO cache timer callback schedules time_work, and time_work can rearm the timer through vc4_bo_cache_free_old().
vc4_bo_cache_destroy() deletes the timer and then cancels the work, which does not break that cycle: the work being cancelled can rearm the timer, and the timer then queues work again after teardown.
Use timer_shutdown_sync() instead, so the timer cannot be rearmed and the cycle ends with cancel_work_sync().
From the CVE record · Linux
The drm/vc4 BO cache timer and its work item can rearm each other during teardown, allowing work to be queued after teardown. The input does not specify an attacker-controlled trigger, impact beyond this behavior, or whether access or user interaction is required.
Engineers running Linux kernels with the drm/vc4 driver should check their versions against the vendor advisory; affected versions are not specified.