summaryrefslogtreecommitdiffstats
path: root/drivers/memstick
diff options
context:
space:
mode:
authorZheng Wang <zyytlz.wz@163.com>2023-03-08 00:43:38 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-05-30 12:42:08 +0100
commitdce890c3dfaf631d0a8ac79c2792911f9fc551fa (patch)
tree26601df37273bd924268c7486a74d848ac30b739 /drivers/memstick
parent6d32884ddae973af0262022b17d2a7c329ae952b (diff)
downloadlinux-stable-dce890c3dfaf631d0a8ac79c2792911f9fc551fa.tar.gz
linux-stable-dce890c3dfaf631d0a8ac79c2792911f9fc551fa.tar.bz2
linux-stable-dce890c3dfaf631d0a8ac79c2792911f9fc551fa.zip
memstick: r592: Fix UAF bug in r592_remove due to race condition
[ Upstream commit 63264422785021704c39b38f65a78ab9e4a186d7 ] In r592_probe, dev->detect_timer was bound with r592_detect_timer. In r592_irq function, the timer function will be invoked by mod_timer. If we remove the module which will call hantro_release to make cleanup, there may be a unfinished work. The possible sequence is as follows, which will cause a typical UAF bug. Fix it by canceling the work before cleanup in r592_remove. CPU0 CPU1 |r592_detect_timer r592_remove | memstick_free_host| put_device; | kfree(host); | | | queue_work | &host->media_checker //use Signed-off-by: Zheng Wang <zyytlz.wz@163.com> Link: https://lore.kernel.org/r/20230307164338.1246287-1-zyytlz.wz@163.com Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/memstick')
-rw-r--r--drivers/memstick/host/r592.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/memstick/host/r592.c b/drivers/memstick/host/r592.c
index 4728a42d54b8..edb1b5588b7a 100644
--- a/drivers/memstick/host/r592.c
+++ b/drivers/memstick/host/r592.c
@@ -831,7 +831,7 @@ static void r592_remove(struct pci_dev *pdev)
/* Stop the processing thread.
That ensures that we won't take any more requests */
kthread_stop(dev->io_thread);
-
+ del_timer_sync(&dev->detect_timer);
r592_enable_device(dev, false);
while (!error && dev->req) {