From: sashiko-bot@kernel.org
To: "Johan Hovold" <johan@kernel.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/3] driver core: fix parent lock use-after-free on USB disconnect
Date: Wed, 14 Oct 2026 13:43:43 +0000 [thread overview]
Message-ID: <sashiko-outbox-171376@kernel.org> (raw)
In-Reply-To: <20261014133109.1392265-2-johan@kernel.org>
> USB interfaces should be probed with their parent USB device lock held
> and the USB bus therefore sets the need_parent_lock bus flag so that
> driver core takes the parent lock when needed.
>
> Driver core is only guaranteed to hold a reference to the parent device
> during initial probe however and nothing prevents the device and its
> parent from being deregistered and the parent potentially freed, for
> example, while iterating over devices in driver_attach() or
> bus_rescan_devices_helper().
>
> Since commit 524134d42231 ("USB: don't cancel queued resets when
> unbinding drivers") USB interfaces hold a reference to their parent USB
> device, but a parent hub may still go away while probing a USB device
> (e.g. via the drivers_probe sysfs interface). This can lead to a
> use-after-free when taking the parent device lock before checking the
> [ ... ]
> Fixes: bf74ad5bc417 ("[PATCH] Hold the device's parent's lock during probe and remove")
> Cc: stable@vger.kernel.org # 2.6.16: 524134d42231: USB: don't cancel queued resets when unbinding drivers
> Cc: stable@vger.kernel.org # 2.6.16
> Cc: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: Johan Hovold <johan@kernel.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014133109.1392265-1-johan@kernel.org?part=1
next prev parent reply other threads:[~2026-10-14 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 13:31 [PATCH v2 0/3] driver core: parent lock fixes Johan Hovold
2026-10-14 13:31 ` [PATCH v2 1/3] driver core: fix parent lock use-after-free on USB disconnect Johan Hovold
2026-10-14 13:43 ` sashiko-bot [this message]
2026-10-14 14:49 ` Danilo Krummrich
2026-10-14 14:58 ` Alan Stern
2026-10-14 13:31 ` [PATCH v2 2/3] driver core: take parent lock on deferred probe Johan Hovold
2026-10-14 13:48 ` sashiko-bot
2026-10-14 13:31 ` [PATCH v2 3/3] driver core: take parent lock in async device attach Johan Hovold
2026-10-14 13:40 ` sashiko-bot
2026-10-14 14:52 ` Alan Stern
2026-10-14 14:58 ` Johan Hovold
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=sashiko-outbox-171376@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.