From: Hans de Goede <hansg@kernel.org>
To: Cen Zhang <zzzccc427@gmail.com>,
Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
baijiaju1990@gmail.com
Subject: Re: [PATCH] usb: misc: usbio: fix disconnect UAF in client teardown
Date: Thu, 18 Jun 2026 13:22:58 +0200 [thread overview]
Message-ID: <b39be4f6-e63a-43c3-9903-e4e6e0a85cd3@kernel.org> (raw)
In-Reply-To: <20260618104633.3405705-1-zzzccc427@gmail.com>
Hi,
On 18-Jun-26 12:46, Cen Zhang wrote:
> usbio_disconnect() walks usbio->cli_list in reverse while each
> auxiliary_device_uninit() can drop the last device reference and run
> usbio_auxdev_release(). If that happens, the current struct usbio_client is
> freed before list_for_each_entry_reverse() advances by reading
> client->link.prev.
>
> Use list_for_each_entry_safe_reverse()
Ack that is good.
> and delete the list node before
> uninitializing the auxiliary device.
Why I see no reason to delete the list node here ?
Regards,
Hans
> The next cursor is then captured before
> the put_device() path can free the current client, and cli_list does not retain
> stale nodes during teardown.
>
> Validation reproduced this kernel report:
> KASAN slab-use-after-free in usbio_disconnect+0x12e/0x150
> Workqueue: usb_hub_wq hub_event
> Read of size 8
> Call trace:
> dump_stack_lvl+0x66/0xa0
> print_report+0xce/0x630
> usbio_disconnect+0x12e/0x150 (drivers/usb/misc/usbio.c:518)
> srso_alias_return_thunk+0x5/0xfbef5
> __virt_addr_valid+0x188/0x320
> kasan_report+0xe0/0x110
> usb_unbind_interface+0xf3/0x400
> __device_attach_driver+0xf1/0x1a0
> bus_for_each_drv+0xf9/0x160
> trace_hardirqs_on+0x18/0x130
> _raw_spin_unlock_irqrestore+0x44/0x60
> __device_attach+0x133/0x2a0
> do_raw_spin_unlock+0x9a/0x100
> device_add+0x9b9/0xc10
> lockdep_hardirqs_on_prepare+0xea/0x1a0
> usb_enable_lpm+0x3c/0x260
> usb_set_configuration+0xb64/0xf20
> add_device_randomness+0xb7/0xf0
> usb_new_device+0x492/0x870
> hub_event+0x1b10/0x29c0
> lock_acquire+0x187/0x300
> process_one_work+0x475/0xb90 (kernel/workqueue.c:3200)
> lock_release+0xc8/0x290
> process_one_work+0x4d7/0xb90 (kernel/workqueue.c:3200)
> __list_add_valid_or_report+0x37/0xf0
> worker_thread+0x2d8/0x570
> kthread+0x1ad/0x1f0
> ret_from_fork+0x3c9/0x540
> __switch_to+0x2e9/0x730
> ret_from_fork_asm+0x1a/0x30
>
> Fixes: 121a0f839dbb ("usb: misc: Add Intel USBIO bridge driver")
> Assisted-by: Codex:gpt-5.5
> Signed-off-by: Cen Zhang <zzzccc427@gmail.com>
> ---
> drivers/usb/misc/usbio.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/misc/usbio.c b/drivers/usb/misc/usbio.c
> index 02d1e0760f0c..7dc44bbcafd2 100644
> --- a/drivers/usb/misc/usbio.c
> +++ b/drivers/usb/misc/usbio.c
> @@ -518,7 +518,7 @@ static int usbio_resume(struct usb_interface *intf)
> static void usbio_disconnect(struct usb_interface *intf)
> {
> struct usbio_device *usbio = usb_get_intfdata(intf);
> - struct usbio_client *client;
> + struct usbio_client *client, *next;
>
> /* Wakeup any clients waiting for a reply */
> usbio->rxdat_len = 0;
> @@ -535,7 +535,8 @@ static void usbio_disconnect(struct usb_interface *intf)
> usb_kill_urb(usbio->urb);
> usb_free_urb(usbio->urb);
>
> - list_for_each_entry_reverse(client, &usbio->cli_list, link) {
> + list_for_each_entry_safe_reverse(client, next, &usbio->cli_list, link) {
> + list_del_init(&client->link);
> auxiliary_device_delete(&client->auxdev);
> auxiliary_device_uninit(&client->auxdev);
> }
next prev parent reply other threads:[~2026-06-18 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 10:46 [PATCH] usb: misc: usbio: fix disconnect UAF in client teardown Cen Zhang
2026-06-18 11:22 ` Hans de Goede [this message]
2026-06-18 12:24 ` Cen Zhang
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=b39be4f6-e63a-43c3-9903-e4e6e0a85cd3@kernel.org \
--to=hansg@kernel.org \
--cc=baijiaju1990@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=israel.a.cepeda.lopez@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=zzzccc427@gmail.com \
/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