From: Greg KH <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: syzbot <syzbot+df9e891bf8ea586f846b@syzkaller.appspotmail.com>,
asml.silence@gmail.com, axboe@kernel.dk, brauner@kernel.org,
io-uring@vger.kernel.org, jack@suse.cz, kartikey406@gmail.com,
kees@kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, mjguzik@gmail.com, nogikh@google.com,
syzbot@kernel.org, syzbot@lists.linux.dev,
syzkaller-bugs@googlegroups.com,
syzkaller-upstream-moderation@googlegroups.com,
torvalds@ppc970.osdl.org, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Read in ep_open
Date: Tue, 18 Aug 2026 09:42:34 +0200 [thread overview]
Message-ID: <2026081849-flatbed-unashamed-a52d@gregkh> (raw)
In-Reply-To: <16741050-a3e2-4193-bfca-232a615a1311@rowland.harvard.edu>
On Mon, Aug 17, 2026 at 02:14:17PM -0400, Alan Stern wrote:
> On Mon, Aug 17, 2026 at 09:38:02AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot has tested the proposed patch and the reproducer did not trigger any issue:
> >
> > Reported-by: syzbot+df9e891bf8ea586f846b@syzkaller.appspotmail.com
> > Tested-by: syzbot+df9e891bf8ea586f846b@syzkaller.appspotmail.com
> >
> > Tested on:
> >
> > commit: 8d3ae592 Linux 7.2
> > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ v7.2
> > console output: https://syzkaller.appspot.com/x/log.txt?x=16a91a25580000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=c44651ea7dd2f307
> > dashboard link: https://syzkaller.appspot.com/bug?extid=df9e891bf8ea586f846b
> > compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
> > patch: https://syzkaller.appspot.com/x/patch.diff?x=15790679580000
> >
> > Note: testing is done by a robot and is best-effort only.
>
> Greg:
>
> Has this patch ever been queued?
>
> https://lore.kernel.org/linux-usb/ee41fbfd-f368-4a06-95d6-ae9b4267fd82@mail.kernel.org/
No because it looks like there are competing patches here as you point
out.
> Looks like you can add syzbot's Tested-by: tag, as well as my Acked-by:.
>
> Note that a different patch to fix the same problem was submitted here:
>
> https://lore.kernel.org/linux-usb/20260731230603.4637-1-kartikey406@gmail.com/
>
> IMO the first patch above is superior.
So Aleksandr's patch should be applied and not Deepanshu's?
thanks,
greg k-h
next prev parent reply other threads:[~2026-08-18 7:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 1:28 [syzbot] [usb?] KASAN: slab-use-after-free Read in ep_open syzbot
2026-08-17 13:42 ` syzbot
2026-08-17 15:04 ` Jens Axboe
2026-08-17 15:45 ` Alan Stern
2026-08-17 16:38 ` syzbot
2026-08-17 18:14 ` Alan Stern
2026-08-18 7:42 ` Greg KH [this message]
2026-08-18 15:37 ` Alan Stern
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=2026081849-flatbed-unashamed-a52d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=jack@suse.cz \
--cc=kartikey406@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=nogikh@google.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+df9e891bf8ea586f846b@syzkaller.appspotmail.com \
--cc=syzbot@kernel.org \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller-upstream-moderation@googlegroups.com \
--cc=torvalds@ppc970.osdl.org \
--cc=viro@zeniv.linux.org.uk \
/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