From: Kees Cook <keescook@chromium.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-input <linux-input@vger.kernel.org>,
srinivas pandruvada <srinivas.pandruvada@intel.com>
Subject: Re: [PATCH 12/14] HID: sensor-hub: validate feature report details
Date: Wed, 4 Sep 2013 09:05:44 -0700 [thread overview]
Message-ID: <CAGXu5jJ4zFJ78=85T6QZDVXZ9GEM_vgbEP4hERjRwQP3RXYkjQ@mail.gmail.com> (raw)
In-Reply-To: <20130829100313.GG7393@intel.com>
Jiri,
Should this one have been part of the batch you applied? It doesn't
use hid_validate_report().
-Kees
On Thu, Aug 29, 2013 at 3:03 AM, Mika Westerberg
<mika.westerberg@linux.intel.com> wrote:
> On Wed, Aug 28, 2013 at 10:31:44PM +0200, Jiri Kosina wrote:
>> From: Kees Cook <keescook@chromium.org>
>>
>> A HID device could send a malicious feature report that would cause the
>> sensor-hub HID driver to read past the end of heap allocation, leaking
>> kernel memory contents to the caller.
>>
>> CVE-2013-2898
>>
>> Signed-off-by: Kees Cook <keescook@chromium.org>
>> Cc: stable@kernel.org
>
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
--
Kees Cook
Chrome OS Security
next prev parent reply other threads:[~2013-09-04 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 20:31 [PATCH 12/14] HID: sensor-hub: validate feature report details Jiri Kosina
2013-08-28 20:42 ` Srinivas Pandruvada
2013-08-28 20:42 ` Jiri Kosina
2013-08-28 21:16 ` Kees Cook
2013-08-29 18:13 ` Srinivas Pandruvada
2013-08-29 19:47 ` Kees Cook
2013-08-29 10:03 ` Mika Westerberg
2013-09-04 16:05 ` Kees Cook [this message]
2013-09-04 18:14 ` Jiri Kosina
2013-09-04 18:26 ` Kees Cook
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='CAGXu5jJ4zFJ78=85T6QZDVXZ9GEM_vgbEP4hERjRwQP3RXYkjQ@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=srinivas.pandruvada@intel.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.