From: Johan Hovold <johan@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] USB: serial: fix port tear down use-after-free
Date: Fri, 21 Aug 2026 17:45:42 +0200 [thread overview]
Message-ID: <20260821154546.118809-1-johan@kernel.org> (raw)
When addressing a port probe ordering issue in digi_acceleport recently
I realised that we have a corresponding general problem during
disconnect, but I didn't have time to address it straight away.
Now syzbot has managed to trigger one of its symptoms and people have
already started submitting incomplete band-aids so here is a proper
fix.
When testing the fix I also noticed that we have an ordering issue when
deregistering drivers that can result in similar use-after-free.
Johan
Changes in v2:
- fix dynamic id driver deregistration race (new)
- remove "new_id" attributes before deregistering USB driver
- use iterator for driver deregistration (new)
Johan Hovold (4):
USB: serial: fix port tear down use-after-free
USB: serial: fix dynamic id driver deregistration race
USB: serial: fix driver deregistration order
USB: serial: use iterator for driver deregistration
drivers/usb/serial/bus.c | 6 +++++-
drivers/usb/serial/usb-serial.c | 32 ++++++++++++++++++++++++++------
include/linux/usb/serial.h | 1 +
3 files changed, 32 insertions(+), 7 deletions(-)
--
2.54.0
next reply other threads:[~2026-08-21 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 15:45 Johan Hovold [this message]
2026-08-21 15:45 ` [PATCH v2 1/4] USB: serial: fix port tear down use-after-free Johan Hovold
2026-08-21 15:45 ` [PATCH v2 2/4] USB: serial: fix dynamic id driver deregistration race Johan Hovold
2026-08-21 15:45 ` [PATCH v2 3/4] USB: serial: fix driver deregistration order Johan Hovold
2026-08-21 15:45 ` [PATCH v2 4/4] USB: serial: use iterator for driver deregistration 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=20260821154546.118809-1-johan@kernel.org \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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