In the Linux kernel, the following vulnerability has been resolved: scsi: dc395x: sync the waiting_timer before freeing the host The waiting_timer callback re-arms itself and takes the host lock. adapter_uninit() currently stops it with timer_delete(), which does not wait for a callback already running on another CPU. The final scsi_host_put() that frees the host (and the host lock the callback dereferences) runs right after adapter_uninit(), so a concurrent or just re-armed callback can fire after the free, leaving a potential use-after-free window. Replace timer_delete() with timer_shutdown_sync() at the top of adapter_uninit(), before the host-lock section: the timer is dequeued, a running callback is waited for and rearming is blocked before the chip is halted, so it cannot fire at all once the adapter has ceased to function. Waiting outside the lock avoids the self-deadlock that would result from syncing a callback blocked on the lock we still hold. No shutdown is needed for selto_timer because it has no reachable armer or callback. This issue was found by an in-house static analysis tool.
https://git.kernel.org/stable/c/bd04acf9b9d589d93823bfeeea9932cd9ce4ee48
https://git.kernel.org/stable/c/a79de0e5e66bd0b69b38c855413a9e3a82926b24
https://git.kernel.org/stable/c/0b65c96e51e6aac86f2db251b5bdc5255294a107
https://git.kernel.org/stable/c/0b1a79f2791a06f139dce5450e487307cf0e241f