From: Oliver Neukum <oneukum@suse.com>
To: Alan Stern <stern@rowland.harvard.edu>,
syzbot <syzbot+d6b0b0ea0781c14b2ecf@syzkaller.appspotmail.com>,
Oliver Neukum <oneukum@suse.com>
Cc: arnd@arndb.de, christian.brauner@ubuntu.com,
gregkh@linuxfoundation.org, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mpe@ellerman.id.au, oleg@redhat.com,
syzkaller-bugs@googlegroups.com, web@syzkaller.appspotmail.com
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Write in usb_anchor_suspend_wakeups
Date: Thu, 17 Aug 2023 14:16:26 +0200 [thread overview]
Message-ID: <5919c39c-1ee4-262b-4ba1-f0e58088611d@suse.com> (raw)
In-Reply-To: <1134d446-3189-4f2d-81b4-10142e751320@rowland.harvard.edu>
On 12.08.23 17:56, Alan Stern wrote:
Hi,
> The real problem seems to be some sort of race in usbtmc and the core
> between URBs being added to an anchor, file I/O being stopped, and URBs
> being killed or scuttled when the file is flushed.
just to make sure, you think it is failing here:
usb_anchor_resume_wakeups(anchor);
because we cannot guarantee that the anchor pointer
is still valid, unless we refcount anchors, which would
make embedding them impossible?
Regards
Oliver
next prev parent reply other threads:[~2023-08-17 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 16:53 [syzbot] [usb?] KASAN: slab-use-after-free Write in usb_anchor_suspend_wakeups syzbot
2023-08-12 9:51 ` syzbot
2023-08-12 15:56 ` Alan Stern
2023-08-17 12:16 ` Oliver Neukum [this message]
2023-08-17 14:12 ` Alan Stern
[not found] <20230502040924.3458-1-hdanton@sina.com>
2023-05-02 4:30 ` syzbot
[not found] <20230502070029.3525-1-hdanton@sina.com>
2023-05-02 7:22 ` syzbot
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=5919c39c-1ee4-262b-4ba1-f0e58088611d@suse.com \
--to=oneukum@suse.com \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+d6b0b0ea0781c14b2ecf@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=web@syzkaller.appspotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).