[<prev] [next>] [day] [month] [year] [list]
Message-ID: <cfc6d242-df9d-42cf-b275-08de2da669e8@rowland.harvard.edu>
Date: Mon, 21 Jul 2025 09:51:34 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: "Lecomte, Arnaud" <contact@...aud-lcm.com>
Cc: gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, viro@...iv.linux.org.uk,
snovitoll@...il.com,
syzbot+86b6d7c8bcc66747c505@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [PATCH] usb: mon: Fix slab-out-of-bounds in mon_bin_event due to
unsafe URB transfer_buffer access
On Mon, Jul 21, 2025 at 09:22:40AM +0100, Lecomte, Arnaud wrote:
> Hi Alan, thanks for your reply.
>
> Your point raises an important question for me: Is there a specific reason
> why we don’t have
> a synchronization mechanism in place to protect the URB's transfer buffer ?
Protect it from what? Access by some driver at an inappropriate time?
Drivers are supposed to know (and this is alluded to in the kerneldoc
for usb_submit_urb()) that they aren't allowed to touch the transfer
buffer while an URB is queued.
Alan Stern
Powered by blists - more mailing lists