In the Linux kernel, the following vulnerability has been resolved: power: supply: twl4030_charger: cancel workers via devm bci is devm-allocated. Two workers (bci->work and bci->current_worker) dereference it. twl4030_bci_remove() disables charging and masks interrupts. It cancels neither worker. A worker pending at remove() can run after devm frees bci. The USB transceiver comes from devm_usb_get_phy_by_node(). devm unregisters its notifier only after remove() returns. A cancel_work_sync() in remove() can then race a notifier reschedule. devm_work_autocancel() and devm_delayed_work_autocancel() avoid that. They cancel the workers during devm release, before bci is freed. The current_worker is registered first, since devm will cancel in reverse order and bci->work can reschedule current_worker. [Move comment about order into the commit message]
https://git.kernel.org/stable/c/b955da82db4170bdf1c784dc457287aa0c977378
https://git.kernel.org/stable/c/a4460e89d4088cfec2da5be33e265ef1a8e780e9
https://git.kernel.org/stable/c/72a2d6cd049f892853e4e2d8d8fc5e7d0244a458
https://git.kernel.org/stable/c/6eba34732524067da2aad5ddfdfbc641ded10e9e