From: Andre Naujoks <nautsch2@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
davem@davemloft.net, netdev@vger.kernel.org
Cc: linux-can@vger.kernel.org, lifeasageek@gmail.com,
threeearcat@gmail.com, syzkaller@googlegroups.com,
Kyungtae Kim <kt0755@gmail.com>,
linux-stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] can: bcm: check timer values before ktime conversion
Date: Wed, 16 Jan 2019 14:31:11 +0100 [thread overview]
Message-ID: <b0c40e9b-9c18-a8b0-c52b-0e6618eb7f9d@gmail.com> (raw)
In-Reply-To: <20190113183143.10612-1-socketcan@hartkopp.net>
Am 13.01.19 um 19:31 schrieb Oliver Hartkopp:
> Kyungtae Kim detected a potential integer overflow in bcm_[rx|tx]_setup()
> when the conversion into ktime multiplies the given value with NSEC_PER_USEC
> (1000).
>
> Reference: https://marc.info/?l=linux-can&m=154732118819828&w=2
>
> Add a check for the given tv_usec, so that the value stays below one second.
> Additionally limit the tv_sec value to a reasonable value for CAN related
> use-cases of 400 days and ensure all values to be positive.
>
> Reported-by: Kyungtae Kim <kt0755@gmail.com>
> Tested-by: Oliver Hartkopp <socketcan@hartkopp.net>
> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
> Cc: linux-stable <stable@vger.kernel.org> # >= 2.6.26
Acked-by: Andre Naujoks <nautsch2@gmail.com>
Sorry for the late reply, but I seem to have missed the initial send of
v2 of this. I wanted to at least ack it, since I made such a fuss about
the timeouts. :-)
Regards
Andre
> ---
> net/can/bcm.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/net/can/bcm.c b/net/can/bcm.c
> index 0af8f0db892a..d4ae0a1471f3 100644
> --- a/net/can/bcm.c
> +++ b/net/can/bcm.c
> @@ -67,6 +67,9 @@
> */
> #define MAX_NFRAMES 256
>
> +/* limit timers to 400 days for sending/timeouts */
> +#define BCM_TIMER_SEC_MAX (400*24*60*60)
> +
> /* use of last_frames[index].flags */
> #define RX_RECV 0x40 /* received data for this element */
> #define RX_THR 0x80 /* element not been sent due to throttle feature */
> @@ -140,6 +143,22 @@ static inline ktime_t bcm_timeval_to_ktime(struct bcm_timeval tv)
> return ktime_set(tv.tv_sec, tv.tv_usec * NSEC_PER_USEC);
> }
>
> +/* check limitations for timeval provided by user */
> +static int bcm_is_invalid_tv(struct bcm_msg_head *msg_head)
> +{
> + if ((msg_head->ival1.tv_sec < 0) ||
> + (msg_head->ival1.tv_sec > BCM_TIMER_SEC_MAX) ||
> + (msg_head->ival1.tv_usec < 0) ||
> + (msg_head->ival1.tv_usec >= USEC_PER_SEC) ||
> + (msg_head->ival2.tv_sec < 0) ||
> + (msg_head->ival2.tv_sec > BCM_TIMER_SEC_MAX) ||
> + (msg_head->ival2.tv_usec < 0) ||
> + (msg_head->ival2.tv_usec >= USEC_PER_SEC))
> + return 1;
> +
> + return 0;
> +}
> +
> #define CFSIZ(flags) ((flags & CAN_FD_FRAME) ? CANFD_MTU : CAN_MTU)
> #define OPSIZ sizeof(struct bcm_op)
> #define MHSIZ sizeof(struct bcm_msg_head)
> @@ -873,6 +892,10 @@ static int bcm_tx_setup(struct bcm_msg_head *msg_head, struct msghdr *msg,
> if (msg_head->nframes < 1 || msg_head->nframes > MAX_NFRAMES)
> return -EINVAL;
>
> + /* check timeval limitations */
> + if ((msg_head->flags & SETTIMER) && bcm_is_invalid_tv(msg_head))
> + return -EINVAL;
> +
> /* check the given can_id */
> op = bcm_find_op(&bo->tx_ops, msg_head, ifindex);
> if (op) {
> @@ -1053,6 +1076,10 @@ static int bcm_rx_setup(struct bcm_msg_head *msg_head, struct msghdr *msg,
> (!(msg_head->can_id & CAN_RTR_FLAG))))
> return -EINVAL;
>
> + /* check timeval limitations */
> + if ((msg_head->flags & SETTIMER) && bcm_is_invalid_tv(msg_head))
> + return -EINVAL;
> +
> /* check the given can_id */
> op = bcm_find_op(&bo->rx_ops, msg_head, ifindex);
> if (op) {
>
next prev parent reply other threads:[~2019-01-16 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 18:31 [PATCH v2] can: bcm: check timer values before ktime conversion Oliver Hartkopp
2019-01-16 13:17 ` Kyungtae Kim
2019-01-16 13:31 ` Andre Naujoks [this message]
2019-01-17 16:04 ` Oliver Hartkopp
[not found] ` <20190116133603.25A5A20873@mail.kernel.org>
2019-01-16 15:05 ` Oliver Hartkopp
2019-01-16 15:54 ` Oliver Hartkopp
2019-01-22 10:26 ` Marc Kleine-Budde
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=b0c40e9b-9c18-a8b0-c52b-0e6618eb7f9d@gmail.com \
--to=nautsch2@gmail.com \
--cc=davem@davemloft.net \
--cc=kt0755@gmail.com \
--cc=lifeasageek@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=stable@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=threeearcat@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;
as well as URLs for NNTP newsgroup(s).