All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: roswest <roswest@cisco.com>
Cc: linux-input@vger.kernel.org, Christopher Kopek <ckopek@cisco.com>
Subject: Re: USB vulnerabilities
Date: Thu, 28 Jul 2016 10:48:48 -0700	[thread overview]
Message-ID: <20160728174848.GA16852@dtor-ws> (raw)
In-Reply-To: <4bb833c7-1e7b-fc19-7ad5-b4e881897d9a@cisco.com>

Hi Rosie,

On Thu, Jul 28, 2016 at 12:23:09PM -0400, roswest wrote:
> 
> Dmitry,
> 
> Hi, I am an engineer at Cisco Systems, and this summer we tasked some
> interns with performing USB fuzzing. One of the interns, Anirudh Bagde,
> was able to crash the USB stack due to an error in the iforce module and
> discovered a buffer over-read in the usbtouchscreen module.  Please see
> the attachment for details.

Thank you for the report. Any chance Anirudh could provide patches to
fix these issues as well?

Thanks!

-- 
Dmitry

  reply	other threads:[~2016-07-28 17:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 16:23 USB vulnerabilities roswest
2016-07-28 17:48 ` Dmitry Torokhov [this message]
2016-07-28 20:58   ` roswest
2016-07-30  0:48     ` Rosie Hall
2016-07-31  1:14       ` Dmitry Torokhov
2016-08-02  4:37         ` Anirudh Bagde

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=20160728174848.GA16852@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=ckopek@cisco.com \
    --cc=linux-input@vger.kernel.org \
    --cc=roswest@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.