From: "Secunia Research" <vuln@secunia.com>
To: "'Shuah Khan'" <shuahkh@osg.samsung.com>, <shuah@kernel.org>,
<valentina.manea.m@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vuln@secunia.com>
Subject: RE: [PATCH 0/4] USB over IP Secuurity fixes
Date: Fri, 8 Dec 2017 16:14:33 +0100 [thread overview]
Message-ID: <000001d37037$40f64570$c2e2d050$@secunia.com> (raw)
In-Reply-To: <cover.1512672005.git.shuahkh@osg.samsung.com>
Hi Shuah,
Thanks a lot for the quick fixes.
Please, use this email address: vuln@secunia.com
We have assigned the following CVEs to the issues:
CVE-2017-16911 usbip: prevent vhci_hcd driver from leaking a socket pointer
address
CVE-2017-16912 usbip: fix stub_rx: get_pipe() to validate endpoint number
CVE-2017-16913 usbip: fix stub_rx: harden CMD_SUBMIT path to handle
malicious input
CVE-2017-16914 usbip: fix stub_send_ret_submit() vulnerability to null
transfer_buffer
Please, let me know if we should proceed with a coordinated disclosure. I'm
not quite sure how many distros / downstreams actually use this
functionality.
Best Regards,
Jakub
-----Original Message-----
From: Shuah Khan [mailto:shuahkh@osg.samsung.com]
Sent: Thursday, December 7, 2017 10:17 PM
To: shuah@kernel.org; valentina.manea.m@gmail.com;
gregkh@linuxfoundation.org
Cc: Shuah Khan <shuahkh@osg.samsung.com>; linux-usb@vger.kernel.org;
linux-kernel@vger.kernel.org; vuln@secunia.com
Subject: [PATCH 0/4] USB over IP Secuurity fixes
Jakub Jirasek from Secunia Research at Flexera reported security
vulnerabilities in the USB over IP driver. This patch series all the 4
reported problems.
Jakub, could you please suggest an email address I can use for the
Reported-by tag?
Shuah Khan (4):
usbip: fix stub_rx: get_pipe() to validate endpoint number
usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input
usbip: prevent vhci_hcd driver from leaking a socket pointer address
usbip: fix stub_send_ret_submit() vulnerability to null
transfer_buffer
drivers/usb/usbip/stub_rx.c | 51
+++++++++++++++++++++++++++++-------
drivers/usb/usbip/stub_tx.c | 7 +++++
drivers/usb/usbip/usbip_common.h | 1 +
drivers/usb/usbip/vhci_sysfs.c | 25 +++++++++++-------
tools/usb/usbip/libsrc/vhci_driver.c | 8 +++---
5 files changed, 69 insertions(+), 23 deletions(-)
--
2.14.1
next prev parent reply other threads:[~2017-12-08 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 21:16 [PATCH 0/4] USB over IP Secuurity fixes Shuah Khan
2017-12-07 21:16 ` [PATCH 1/4] usbip: fix stub_rx: get_pipe() to validate endpoint number Shuah Khan
2017-12-07 21:16 ` [PATCH 2/4] usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input Shuah Khan
2017-12-07 21:16 ` [PATCH 3/4] usbip: prevent vhci_hcd driver from leaking a socket pointer address Shuah Khan
2017-12-07 21:16 ` [PATCH 4/4] usbip: fix stub_send_ret_submit() vulnerability to null transfer_buffer Shuah Khan
2017-12-08 6:25 ` [PATCH 0/4] USB over IP Secuurity fixes Greg KH
2017-12-08 15:41 ` Shuah Khan
2017-12-08 15:14 ` Secunia Research [this message]
2017-12-08 15:44 ` Shuah Khan
2017-12-08 16:33 ` Greg KH
2017-12-08 16:41 ` Shuah Khan
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='000001d37037$40f64570$c2e2d050$@secunia.com' \
--to=vuln@secunia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=valentina.manea.m@gmail.com \
/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