In the Linux kernel, the following vulnerability has been resolved: klist: avoid accesses after waking klist_remove() klist_remove() waits until a node is unreferenced so that its caller can free the containing object. klist_release() currently publishes waiter->woken and wakes the waiter before its final accesses to the waiter and node. klist_remove() can then return, allowing its stack waiter and the containing object to be freed or reused while klist_release() is still running. In particular, bus_remove_driver() can free drv->p while __device_attach() walks the same bus klist with bus_for_each_drv(). On an arm64 Cortex-A72 system, an unpatched 7.2.0-rc3 kernel with CONFIG_PREEMPT_RT=y and CONFIG_KASAN=y reproduced the bug through the in-tree I2C/at24 path. KASAN reported a use-after-free in klist_dec_and_del() reached from klist_next()/bus_for_each_drv() while at24 was being unregistered. Clear n_klist and take a task reference before publishing woken. Use release/acquire accesses for that publication and wake the referenced task. The task reference keeps the waiter task alive if it returns and exits before wake_up_process().
https://git.kernel.org/stable/c/d655ef174056457d1c3bc06b4405097e0a9b3bf5
https://git.kernel.org/stable/c/7d3df012573523cb2f38a65e3e00125d9869b390
https://git.kernel.org/stable/c/732e3e10234cbe302d0dcbaa98c91c66628209cb
https://git.kernel.org/stable/c/3fee2a5ef405f08ea3d87d2014ae7d38e61dd06f