[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d7ea3cfd8bde4b8ba7ed6ea4c545c9dc@realtek.com>
Date: Fri, 14 May 2021 10:32:24 +0000
From: Hayes Wang <hayeswang@...ltek.com>
To: Greg KH <greg@...ah.com>
CC: Alan Stern <stern@...land.harvard.edu>,
syzbot <syzbot+95afd23673f5dd295c57@...kaller.appspotmail.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
nic_swsd <nic_swsd@...ltek.com>
Subject: RE: [syzbot] WARNING in rtl8152_probe
Greg KH <greg@...ah.com>
> Sent: Friday, May 14, 2021 4:27 PM
[...]
> Checking the whole USB decriptor is fine, yes, they can duplicate that.
> So that means you need to validate _ALL_ data coming from the device
> that it is in an acceptable range of values that the driver can
> correctly handle.
I see.
Best Regards,
Hayes
Powered by blists - more mailing lists