From: Johan Hovold <johan@kernel.org>
To: Fan Wu <fanwu01@zju.edu.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: serial: opticon: fix UAF in write callback during port removal
Date: Tue, 10 Mar 2026 09:56:48 +0100 [thread overview]
Message-ID: <aa_c0B9E7MPm_yqL@hovoldconsulting.com> (raw)
In-Reply-To: <20260309142757.589802-1-fanwu01@zju.edu.cn>
On Mon, Mar 09, 2026 at 02:27:57PM +0000, Fan Wu wrote:
> The opticon driver anchors write URBs to priv->anchor in opticon_write()
> and frees priv in opticon_port_remove() without first killing these
> anchored URBs. The completion callback opticon_write_control_callback()
> may dereference priv via usb_get_serial_port_data() and access
> priv->lock, priv->outstanding_urbs, and priv->outstanding_bytes after
> it has been freed.
>
> If a write URB is in flight when the port is removed:
>
> CPU 0 (remove path) CPU 1 (URB completion)
> --------------------- ---------------------
> opticon_port_remove()
> kfree(priv) <--+
> | --> opticon_write_control_callback()
> | priv = usb_get_serial_port_data()
> | spin_lock_irqsave(&priv->lock)
> | --priv->outstanding_urbs // possible UAF
> return |
> usb_free_urb()
This cannot happen as ports are always shut down before being
deregistered (see usb_serial_disconnect()).
It used to be possible to trigger something like this by manually
unbinding a port device through sysfs as root but even that's no longer
possible since commit fdb838efa31e ("USB: serial: suppress driver bind
attributes").
> Fix this by calling usb_kill_anchored_urbs(&priv->anchor) before
> kfree(priv) so that all in-flight URBs have finished before the private
> data is freed.
>
> Note that opticon_close() already correctly kills anchored URBs; this
> fix addresses the port_remove path which was overlooked.
>
> Fixes: 648d4e16567e ("USB: serial: opticon: add write support")
> Signed-off-by: Fan Wu <fanwu01@zju.edu.cn>
How was this potential issue found? Are you using some kind of LLM or
other tool?
Johan
next prev parent reply other threads:[~2026-03-10 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:27 [PATCH] USB: serial: opticon: fix UAF in write callback during port removal Fan Wu
2026-03-10 8:56 ` Johan Hovold [this message]
2026-03-10 17:04 ` Fan Wu
2026-03-11 12:14 ` Greg Kroah-Hartman
2026-03-11 14:26 ` Fan Wu
2026-03-11 15:41 ` 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=aa_c0B9E7MPm_yqL@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=fanwu01@zju.edu.cn \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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