From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] [media] firewire: firedtv-avc: potential buffer overflow
Date: Mon, 08 Sep 2014 12:05:02 +0000 [thread overview]
Message-ID: <20140908140502.20d6f864@kant> (raw)
In-Reply-To: <20140908111843.GC6947@mwanda>
On Sep 08 Dan Carpenter wrote:
> "program_info_length" is user controlled and can go up to 4095. The
> operand[] array has 509 bytes so we need to add a limit here to prevent
> buffer overflows.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Thank you.
>
> diff --git a/drivers/media/firewire/firedtv-avc.c b/drivers/media/firewire/firedtv-avc.c
> index d1a1a13..ac17567 100644
> --- a/drivers/media/firewire/firedtv-avc.c
> +++ b/drivers/media/firewire/firedtv-avc.c
> @@ -1157,6 +1157,10 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length)
> if (pmt_cmd_id != 1 && pmt_cmd_id != 4)
> dev_err(fdtv->device,
> "invalid pmt_cmd_id %d\n", pmt_cmd_id);
> + if (program_info_length > sizeof(c->operand) - write_pos) {
> + ret = -EINVAL;
> + goto out;
> + }
>
> memcpy(&c->operand[write_pos], &msg[read_pos],
> program_info_length);
> @@ -1180,6 +1184,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length)
> dev_err(fdtv->device, "invalid pmt_cmd_id %d "
> "at stream level\n", pmt_cmd_id);
>
> + if (es_info_length > sizeof(c->operand) - write_pos) {
> + ret = -EINVAL;
> + goto out;
> + }
> +
> memcpy(&c->operand[write_pos], &msg[read_pos],
> es_info_length);
> read_pos += es_info_length;
--
Stefan Richter
-===-==- =--= -=---
http://arcgraph.de/sr/
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
kernel-janitors@vger.kernel.org
Subject: Re: [patch] [media] firewire: firedtv-avc: potential buffer overflow
Date: Mon, 8 Sep 2014 14:05:02 +0200 [thread overview]
Message-ID: <20140908140502.20d6f864@kant> (raw)
In-Reply-To: <20140908111843.GC6947@mwanda>
On Sep 08 Dan Carpenter wrote:
> "program_info_length" is user controlled and can go up to 4095. The
> operand[] array has 509 bytes so we need to add a limit here to prevent
> buffer overflows.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Reviewed-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Thank you.
>
> diff --git a/drivers/media/firewire/firedtv-avc.c b/drivers/media/firewire/firedtv-avc.c
> index d1a1a13..ac17567 100644
> --- a/drivers/media/firewire/firedtv-avc.c
> +++ b/drivers/media/firewire/firedtv-avc.c
> @@ -1157,6 +1157,10 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length)
> if (pmt_cmd_id != 1 && pmt_cmd_id != 4)
> dev_err(fdtv->device,
> "invalid pmt_cmd_id %d\n", pmt_cmd_id);
> + if (program_info_length > sizeof(c->operand) - write_pos) {
> + ret = -EINVAL;
> + goto out;
> + }
>
> memcpy(&c->operand[write_pos], &msg[read_pos],
> program_info_length);
> @@ -1180,6 +1184,11 @@ int avc_ca_pmt(struct firedtv *fdtv, char *msg, int length)
> dev_err(fdtv->device, "invalid pmt_cmd_id %d "
> "at stream level\n", pmt_cmd_id);
>
> + if (es_info_length > sizeof(c->operand) - write_pos) {
> + ret = -EINVAL;
> + goto out;
> + }
> +
> memcpy(&c->operand[write_pos], &msg[read_pos],
> es_info_length);
> read_pos += es_info_length;
--
Stefan Richter
-=====-====- =--= -=---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2014-09-08 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 11:18 [patch] [media] firewire: firedtv-avc: potential buffer overflow Dan Carpenter
2014-09-08 11:18 ` Dan Carpenter
2014-09-08 12:05 ` Stefan Richter [this message]
2014-09-08 12:05 ` Stefan Richter
2014-09-08 12:40 ` Stefan Richter
2014-09-08 12:40 ` Stefan Richter
2014-09-09 8:36 ` Dan Carpenter
2014-09-09 8:36 ` Dan Carpenter
2014-09-09 12:11 ` [patch v2] " Dan Carpenter
2014-09-09 12:11 ` Dan Carpenter
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=20140908140502.20d6f864@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=m.chehab@samsung.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.