forked from Minki/linux
media: ati_remote: sanity check for both endpoints
If you do sanity checks, you should do them for both endpoints. Hence introduce checking for endpoint type for the output endpoint, too. Reported-by: syzbot+998261c2ae5932458f6c@syzkaller.appspotmail.com Signed-off-by: Oliver Neukum <oneukum@suse.com> Signed-off-by: Sean Young <sean@mess.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
This commit is contained in:
parent
ce5d72b6f5
commit
a8be80053e
@ -835,6 +835,10 @@ static int ati_remote_probe(struct usb_interface *interface,
|
||||
err("%s: endpoint_in message size==0? \n", __func__);
|
||||
return -ENODEV;
|
||||
}
|
||||
if (!usb_endpoint_is_int_out(endpoint_out)) {
|
||||
err("%s: Unexpected endpoint_out\n", __func__);
|
||||
return -ENODEV;
|
||||
}
|
||||
|
||||
ati_remote = kzalloc(sizeof (struct ati_remote), GFP_KERNEL);
|
||||
rc_dev = rc_allocate_device(RC_DRIVER_SCANCODE);
|
||||
|
Loading…
Reference in New Issue
Block a user