From: Johan Hovold <johan@kernel.org>
To: Fan Wu <12321260@zju.edu.cn>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Fan Wu <fanwu01@zju.edu.cn>,
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: Wed, 11 Mar 2026 16:41:20 +0100 [thread overview]
Message-ID: <abGNIEsGtMZsYq6a@hovoldconsulting.com> (raw)
In-Reply-To: <493E1779-94BC-49B3-80CB-3AE5FDD3D045@zju.edu.cn>
On Wed, Mar 11, 2026 at 10:26:33PM +0800, Fan Wu wrote:
> > On Mar 11, 2026, at 20:14, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > On Tue, Mar 10, 2026 at 05:04:24PM +0000, Fan Wu wrote:
> >> On Tue, Mar 10, 2026 at 09:56:48 +0100, Johan Hovold wrote:
> >>> How was this potential issue found? Are you using some kind of LLM or
> >>> other tool?
> >> I'm currently researching static analysis techniques (CodeQL combined with LLM
> >> assistance) for detecting UAF bugs, particularly around cross-entry lifetimes.
> >> In this case, the analysis missed the subsystem-level guarantee that close runs
> >> before remove.
> >
> > As is required, you always have to document this type of thing in the
> > changelog text.
> Thanks for the reminder. Understood — I'll make sure to explicitly document the
> search method and tool assistance in the changelog for any future patches.
Here's a link to the guidelines if you haven't found them already (under
Documentation/ in the kernel tree):
https://docs.kernel.org/process/researcher-guidelines.html
Johan
prev parent reply other threads:[~2026-03-11 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:27 Fan Wu
2026-03-10 8:56 ` Johan Hovold
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 [this message]
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=abGNIEsGtMZsYq6a@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=12321260@zju.edu.cn \
--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
all inboxes | Powered by JetHome®