[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5919c39c-1ee4-262b-4ba1-f0e58088611d@suse.com>
Date: Thu, 17 Aug 2023 14:16:26 +0200
From: Oliver Neukum <oneukum@...e.com>
To: Alan Stern <stern@...land.harvard.edu>,
syzbot <syzbot+d6b0b0ea0781c14b2ecf@...kaller.appspotmail.com>,
Oliver Neukum <oneukum@...e.com>
Cc: arnd@...db.de, christian.brauner@...ntu.com,
gregkh@...uxfoundation.org, hdanton@...a.com,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
mpe@...erman.id.au, oleg@...hat.com,
syzkaller-bugs@...glegroups.com, web@...kaller.appspotmail.com
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Write in
usb_anchor_suspend_wakeups
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
Powered by blists - more mailing lists