In the Linux kernel, the following vulnerability has been resolved: Input: byd - synchronize timer deletion before freeing private data byd_disconnect() uses timer_delete() before freeing the driver's private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress. Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.
https://git.kernel.org/stable/c/ee944a706a18322b4a2599eebe8040a2994e928f
https://git.kernel.org/stable/c/c83e79c0842ed29860648bcce5022ef0ba5001c6
https://git.kernel.org/stable/c/8dbfd8e32a13e116790780ed0be82b5a05eb9916
https://git.kernel.org/stable/c/84b205297fa15f97510342221d8c9a0119711478
https://git.kernel.org/stable/c/2e509ef60ee41a2da0deb062c262bb530143fb37
https://git.kernel.org/stable/c/28d984a66b9e14be74986167b6ad40b5e0daf19a