linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
@ 2017-09-08 17:55 Dmitry Torokhov
  2017-09-13 14:02 ` Jiri Kosina
  2017-09-13 16:18 ` Jiri Kosina
  0 siblings, 2 replies; 6+ messages in thread
From: Dmitry Torokhov @ 2017-09-08 17:55 UTC (permalink / raw)
  To: Jiri Kosina; +Cc: Benjamin Tissoires, Guenter Roeck, linux-input, linux-kernel

From: Adrian Salido <salidoa@google.com>

The buffer allocation is not currently accounting for an extra byte for
the report id. This can cause an out of bounds access in function
i2c_hid_set_or_send_report() with reportID > 15.

Signed-off-by: Guenter Roeck <groeck@chromium.org>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
 drivers/hid/i2c-hid/i2c-hid.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/hid/i2c-hid/i2c-hid.c b/drivers/hid/i2c-hid/i2c-hid.c
index 77396145d2d0..9145c2129a96 100644
--- a/drivers/hid/i2c-hid/i2c-hid.c
+++ b/drivers/hid/i2c-hid/i2c-hid.c
@@ -543,7 +543,8 @@ static int i2c_hid_alloc_buffers(struct i2c_hid *ihid, size_t report_size)
 {
 	/* the worst case is computed from the set_report command with a
 	 * reportID > 15 and the maximum report length */
-	int args_len = sizeof(__u8) + /* optional ReportID byte */
+	int args_len = sizeof(__u8) + /* ReportID */
+		       sizeof(__u8) + /* optional ReportID byte */
 		       sizeof(__u16) + /* data register */
 		       sizeof(__u16) + /* size of the report */
 		       report_size; /* report */
-- 
2.14.1.581.gf28d330327-goog


-- 
Dmitry

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
  2017-09-08 17:55 [PATCH] HID: i2c-hid: allocate hid buffers for real worst case Dmitry Torokhov
@ 2017-09-13 14:02 ` Jiri Kosina
  2017-09-13 14:49   ` Dmitry Torokhov
  2017-09-13 16:18 ` Jiri Kosina
  1 sibling, 1 reply; 6+ messages in thread
From: Jiri Kosina @ 2017-09-13 14:02 UTC (permalink / raw)
  To: Dmitry Torokhov
  Cc: Benjamin Tissoires, Guenter Roeck, linux-input, linux-kernel

On Fri, 8 Sep 2017, Dmitry Torokhov wrote:

> From: Adrian Salido <salidoa@google.com>
> 
> The buffer allocation is not currently accounting for an extra byte for
> the report id. This can cause an out of bounds access in function
> i2c_hid_set_or_send_report() with reportID > 15.
> 
> Signed-off-by: Guenter Roeck <groeck@chromium.org>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

Missing signoff from the patch author?

Also, I think this should have Cc: stable, right?

Thanks,

-- 
Jiri Kosina
SUSE Labs


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
  2017-09-13 14:02 ` Jiri Kosina
@ 2017-09-13 14:49   ` Dmitry Torokhov
  2017-09-13 14:52     ` Jiri Kosina
  0 siblings, 1 reply; 6+ messages in thread
From: Dmitry Torokhov @ 2017-09-13 14:49 UTC (permalink / raw)
  To: Jiri Kosina; +Cc: Benjamin Tissoires, Guenter Roeck, linux-input, linux-kernel

On Wed, Sep 13, 2017 at 07:02:05AM -0700, Jiri Kosina wrote:
> On Fri, 8 Sep 2017, Dmitry Torokhov wrote:
> 
> > From: Adrian Salido <salidoa@google.com>
> > 
> > The buffer allocation is not currently accounting for an extra byte for
> > the report id. This can cause an out of bounds access in function
> > i2c_hid_set_or_send_report() with reportID > 15.
> > 
> > Signed-off-by: Guenter Roeck <groeck@chromium.org>
> > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> 
> Missing signoff from the patch author?

Oops, I must have cut it off on accident while removing ChromeOS
specific tags, the original commit is here:

https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/475212

> 
> Also, I think this should have Cc: stable, right?

I usually let maintainers decide, but yes.

Thanks.

-- 
Dmitry

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
  2017-09-13 14:49   ` Dmitry Torokhov
@ 2017-09-13 14:52     ` Jiri Kosina
  2017-09-13 15:00       ` Benson Leung
  0 siblings, 1 reply; 6+ messages in thread
From: Jiri Kosina @ 2017-09-13 14:52 UTC (permalink / raw)
  To: Dmitry Torokhov
  Cc: Benjamin Tissoires, Guenter Roeck, linux-input, linux-kernel

On Wed, 13 Sep 2017, Dmitry Torokhov wrote:

> > > From: Adrian Salido <salidoa@google.com>
> > > 
> > > The buffer allocation is not currently accounting for an extra byte for
> > > the report id. This can cause an out of bounds access in function
> > > i2c_hid_set_or_send_report() with reportID > 15.
> > > 
> > > Signed-off-by: Guenter Roeck <groeck@chromium.org>
> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > 
> > Missing signoff from the patch author?
> 
> Oops, I must have cut it off on accident while removing ChromeOS
> specific tags, the original commit is here:
> 
> https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/475212

Ok, thanks, will use that one. How about 

	Reviewed-by: Benson Leung <bleung@chromium.org>

which is missing in the mail you've sent, but is there in the above 
reference commit?

> > Also, I think this should have Cc: stable, right?
> 
> I usually let maintainers decide, but yes.

I'll be adding it. Thanks,

-- 
Jiri Kosina
SUSE Labs


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
  2017-09-13 14:52     ` Jiri Kosina
@ 2017-09-13 15:00       ` Benson Leung
  0 siblings, 0 replies; 6+ messages in thread
From: Benson Leung @ 2017-09-13 15:00 UTC (permalink / raw)
  To: Jiri Kosina
  Cc: Dmitry Torokhov, Benjamin Tissoires, Guenter Roeck, linux-input,
	linux-kernel, bleung

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Hi Jiri,

On Wed, Sep 13, 2017 at 07:52:20AM -0700, Jiri Kosina wrote:
> > Oops, I must have cut it off on accident while removing ChromeOS
> > specific tags, the original commit is here:
> > 
> > https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/475212
> 
> Ok, thanks, will use that one. How about 
> 
> 	Reviewed-by: Benson Leung <bleung@chromium.org>
> 
> which is missing in the mail you've sent, but is there in the above 
> reference commit?

Submission looks good to me. Go ahead and add.
Reviewed-by: Benson Leung <bleung@chromium.org>

Thanks,
Benson
-- 
Benson Leung
Staff Software Engineer
Chrome OS Kernel
Google Inc.
bleung@google.com
Chromium OS Project
bleung@chromium.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] HID: i2c-hid: allocate hid buffers for real worst case
  2017-09-08 17:55 [PATCH] HID: i2c-hid: allocate hid buffers for real worst case Dmitry Torokhov
  2017-09-13 14:02 ` Jiri Kosina
@ 2017-09-13 16:18 ` Jiri Kosina
  1 sibling, 0 replies; 6+ messages in thread
From: Jiri Kosina @ 2017-09-13 16:18 UTC (permalink / raw)
  To: Dmitry Torokhov
  Cc: Benjamin Tissoires, Guenter Roeck, linux-input, linux-kernel

On Fri, 8 Sep 2017, Dmitry Torokhov wrote:

> From: Adrian Salido <salidoa@google.com>
> 
> The buffer allocation is not currently accounting for an extra byte for
> the report id. This can cause an out of bounds access in function
> i2c_hid_set_or_send_report() with reportID > 15.
> 
> Signed-off-by: Guenter Roeck <groeck@chromium.org>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

I've added the missing tags and applied to for-4.14/upstream-fixes

-- 
Jiri Kosina
SUSE Labs

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2017-09-13 16:18 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-09-08 17:55 [PATCH] HID: i2c-hid: allocate hid buffers for real worst case Dmitry Torokhov
2017-09-13 14:02 ` Jiri Kosina
2017-09-13 14:49   ` Dmitry Torokhov
2017-09-13 14:52     ` Jiri Kosina
2017-09-13 15:00       ` Benson Leung
2017-09-13 16:18 ` Jiri Kosina

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).