From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207871] nullpointer dereference in uvc_video_stop_streaming
Date: Sun, 24 May 2020 11:05:23 +0000 [thread overview]
Message-ID: <bug-207871-208809-DIaQkmTNN5@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207871-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207871
--- Comment #2 from Tobias Diedrich (ranma+kernel@tdiedrich.de) ---
Interestingly, usb_set_interface() already calls usb_ifnum_to_if() once, which
did not fail. Then after calling usb_disable_interface() it calls
usb_hcd_alloc_bandwidth(), which does another call to usb_ifnum_to_if(), which
faulted with the null deref.
The fault is at:
mov rax, [rdx + 0x398]
test rax, rax
jz early_exit_since_config_is_null
[...]
mov rcx, [rax + rdx*8 + 0x98]
inc rdx
-> mov r8, [rcx]
movzx r8d, byte ptr [r8 + 2]
[...]
So I think the fault is at
[...]
for (i = 0; i < config->desc.bNumInterfaces; i++)
-> if (config->interface[i]->altsetting[0].desc.bInterfaceNumber == ifnum)
^^^^^^^^^^^^nullptr
return config->interface[i];
[...]
usb_set_interface() only checks for dev->state == USB_STATE_SUSPENDED, maybe it
also needs to check for dev->state == USB_STATE_NOTATTACHED?
The disconnect message indicates this would have been the state the device was
in, from usb_disconnect():
[...]
usb_set_device_state(udev, USB_STATE_NOTATTACHED);
dev_info(&udev->dev, "USB disconnect, device number %d\n", udev->devnum);
[...]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-05-24 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 19:28 [Bug 207871] New: nullpointer dereference in uvc_video_stop_streaming bugzilla-daemon
2020-05-24 11:05 ` bugzilla-daemon [this message]
2020-05-24 14:38 ` [Bug 207871] " bugzilla-daemon
2020-05-24 21:53 ` bugzilla-daemon
2020-05-25 0:41 ` bugzilla-daemon
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=bug-207871-208809-DIaQkmTNN5@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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).