* [PATCH] usb: storage: realtek_cr: fix use-after-free on disconnect
@ 2026-07-27 12:34 Myeonghun Pak
2026-07-27 14:27 ` Alan Stern
0 siblings, 1 reply; 2+ messages in thread
From: Myeonghun Pak @ 2026-07-27 12:34 UTC (permalink / raw)
To: Alan Stern
Cc: Greg Kroah-Hartman, edwin_rong, Ijae Kim, linux-usb, usb-storage,
linux-kernel, stable
realtek_cr_destructor() calls timer_delete() before the chip containing
the timer is freed. The timer callback may still be running and can
rearm itself, resulting in a use-after-free.
Use timer_shutdown_sync() to wait for the callback and prevent further
rearming. Do this unconditionally because ss_en may be changed after
the timer is armed.
Move timer_setup() into init_realtek_cr() so the timer is initialized
before any failure path can invoke the destructor.
Found by static analysis.
Fixes: e931830bb877 ("Realtek cr: Add autosuspend function.")
Cc: stable@vger.kernel.org
Co-developed-by: Ijae Kim <ae878000@gmail.com>
Signed-off-by: Ijae Kim <ae878000@gmail.com>
Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
---
drivers/usb/storage/realtek_cr.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/storage/realtek_cr.c b/drivers/usb/storage/realtek_cr.c
index af038b897c6b..c4b28744693b 100644
--- a/drivers/usb/storage/realtek_cr.c
+++ b/drivers/usb/storage/realtek_cr.c
@@ -916,7 +916,6 @@ static int realtek_cr_autosuspend_setup(struct us_data *us)
us->proto_handler = rts51x_invoke_transport;
chip->timer_expires = 0;
- timer_setup(&chip->rts51x_suspend_timer, rts51x_suspend_timer_fn, 0);
fw5895_init(us);
/* enable autosuspend function of the usb device */
@@ -934,10 +933,7 @@ static void realtek_cr_destructor(void *extra)
return;
#ifdef CONFIG_REALTEK_AUTOPM
- if (ss_en) {
- timer_delete(&chip->rts51x_suspend_timer);
- chip->timer_expires = 0;
- }
+ timer_shutdown_sync(&chip->rts51x_suspend_timer);
#endif
kfree(chip->status);
}
@@ -982,6 +978,9 @@ static int init_realtek_cr(struct us_data *us)
us->extra = chip;
us->extra_destructor = realtek_cr_destructor;
+#ifdef CONFIG_REALTEK_AUTOPM
+ timer_setup(&chip->rts51x_suspend_timer, rts51x_suspend_timer_fn, 0);
+#endif
us->max_lun = chip->max_lun = rts51x_get_max_lun(us);
chip->us = us;
--
2.47.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] usb: storage: realtek_cr: fix use-after-free on disconnect
2026-07-27 12:34 [PATCH] usb: storage: realtek_cr: fix use-after-free on disconnect Myeonghun Pak
@ 2026-07-27 14:27 ` Alan Stern
0 siblings, 0 replies; 2+ messages in thread
From: Alan Stern @ 2026-07-27 14:27 UTC (permalink / raw)
To: Myeonghun Pak
Cc: Greg Kroah-Hartman, edwin_rong, Ijae Kim, linux-usb, usb-storage,
linux-kernel, stable
On Mon, Jul 27, 2026 at 09:34:14PM +0900, Myeonghun Pak wrote:
> realtek_cr_destructor() calls timer_delete() before the chip containing
> the timer is freed. The timer callback may still be running and can
> rearm itself, resulting in a use-after-free.
>
> Use timer_shutdown_sync() to wait for the callback and prevent further
> rearming. Do this unconditionally because ss_en may be changed after
> the timer is armed.
>
> Move timer_setup() into init_realtek_cr() so the timer is initialized
> before any failure path can invoke the destructor.
>
> Found by static analysis.
>
> Fixes: e931830bb877 ("Realtek cr: Add autosuspend function.")
> Cc: stable@vger.kernel.org
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> ---
This is fine as far as it goes, but the real question is why realtek_cr
uses this elaborate suspend machinery instead of just relying on normal
runtime PM.
This material was added in commit e931830bb877e2aa ("Realtek cr: Add
autosuspend function.") with no explanation about why it was so
complicated. Can anyone say why all this complication shouldn't be
removed?
Alan Stern
> drivers/usb/storage/realtek_cr.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/usb/storage/realtek_cr.c b/drivers/usb/storage/realtek_cr.c
> index af038b897c6b..c4b28744693b 100644
> --- a/drivers/usb/storage/realtek_cr.c
> +++ b/drivers/usb/storage/realtek_cr.c
> @@ -916,7 +916,6 @@ static int realtek_cr_autosuspend_setup(struct us_data *us)
> us->proto_handler = rts51x_invoke_transport;
>
> chip->timer_expires = 0;
> - timer_setup(&chip->rts51x_suspend_timer, rts51x_suspend_timer_fn, 0);
> fw5895_init(us);
>
> /* enable autosuspend function of the usb device */
> @@ -934,10 +933,7 @@ static void realtek_cr_destructor(void *extra)
> return;
>
> #ifdef CONFIG_REALTEK_AUTOPM
> - if (ss_en) {
> - timer_delete(&chip->rts51x_suspend_timer);
> - chip->timer_expires = 0;
> - }
> + timer_shutdown_sync(&chip->rts51x_suspend_timer);
> #endif
> kfree(chip->status);
> }
> @@ -982,6 +978,9 @@ static int init_realtek_cr(struct us_data *us)
>
> us->extra = chip;
> us->extra_destructor = realtek_cr_destructor;
> +#ifdef CONFIG_REALTEK_AUTOPM
> + timer_setup(&chip->rts51x_suspend_timer, rts51x_suspend_timer_fn, 0);
> +#endif
> us->max_lun = chip->max_lun = rts51x_get_max_lun(us);
> chip->us = us;
>
> --
> 2.47.1
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-07-27 14:27 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-27 12:34 [PATCH] usb: storage: realtek_cr: fix use-after-free on disconnect Myeonghun Pak
2026-07-27 14:27 ` Alan Stern
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox