From: Greg KH <gregkh@linuxfoundation.org>
To: Jimmy Hu <hhhuuu@google.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: udc: fix race condition in usb_del_gadget
Date: Thu, 9 Oct 2025 06:58:34 +0200 [thread overview]
Message-ID: <2025100927-pantry-acre-f9a8@gregkh> (raw)
In-Reply-To: <20251009022150.302915-1-hhhuuu@google.com>
On Thu, Oct 09, 2025 at 02:21:49AM +0000, Jimmy Hu wrote:
> A race condition during gadget teardown can lead to a use-after-free
> in usb_gadget_state_work(), as reported by KASAN:
>
> BUG: KASAN: invalid-access in sysfs_notify+0_x_2c/0_x_d0
> Workqueue: events usb_gadget_state_work
>
> The fundamental race occurs because a concurrent event (e.g., an
> interrupt) can call usb_gadget_set_state() and schedule gadget->work
> at any time during the cleanup process in usb_del_gadget().
>
> Commit 399a45e5237c ("usb: gadget: core: flush gadget workqueue after
> device removal") attempted to fix this by moving flush_work() to after
> device_del(). However, this does not fully solve the race, as a new
> work item can still be scheduled *after* flush_work() completes but
> before the gadget's memory is freed, leading to the same use-after-free.
>
> This patch fixes the race condition robustly by introducing a 'teardown'
> flag and a 'state_lock' spinlock to the usb_gadget struct. The flag is
> set during cleanup in usb_del_gadget() *before* calling flush_work() to
> prevent any new work from being scheduled once cleanup has commenced.
> The scheduling site, usb_gadget_set_state(), now checks this flag under
> the lock before queueing the work, thus safely closing the race window.
>
> Fixes: 5702f75375aa9 ("usb: gadget: udc-core: move sysfs_notify() to a workqueue")
> Signed-off-by: Jimmy Hu <hhhuuu@google.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/usb/gadget/udc/core.c | 18 +++++++++++++++++-
> include/linux/usb/gadget.h | 6 ++++++
> 2 files changed, 23 insertions(+), 1 deletion(-)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2025-10-09 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 2:21 [PATCH] usb: gadget: udc: fix race condition in usb_del_gadget Jimmy Hu
2025-10-09 4:58 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-13 7:57 Jimmy Hu
2025-10-13 13:30 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025100927-pantry-acre-f9a8@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hhhuuu@google.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox