mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Anant Thazhemadam <anant.thazhemadam@gmail.com>,
	Oliver Hartkopp <socketcan@hartkopp.net>,
	"David S . Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	syzbot+9bcb0c9409066696d3aa@syzkaller.appspotmail.com
Subject: Re: [PATCH] net: can: prevent potential access of uninitialized value in canfd_rcv()
Date: Mon, 2 Nov 2020 08:10:59 +0100	[thread overview]
Message-ID: <1817819d-3aeb-8034-a4ec-7c70040b0cf0@pengutronix.de> (raw)
In-Reply-To: <20201102031326.430048-1-anant.thazhemadam@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2770 bytes --]

On 11/2/20 4:13 AM, Anant Thazhemadam wrote:
> In canfd_rcv(), cfd->len is uninitialized when skb->len = 0, and this
> uninitialized cfd->len is accessed nonetheless by pr_warn_once().
> 
> Fix this uninitialized variable access by checking cfd->len's validity
> condition (cfd->len > CANFD_MAX_DLEN) separately after the skb->len's
> condition is checked, and appropriately modify the log messages that
> are generated as well.
> In case either of the required conditions fail, the skb is freed and
> NET_RX_DROP is returned, same as before.
> 
> Reported-by: syzbot+9bcb0c9409066696d3aa@syzkaller.appspotmail.com
> Tested-by: Anant Thazhemadam <anant.thazhemadam@gmail.com>
> Signed-off-by: Anant Thazhemadam <anant.thazhemadam@gmail.com>
> ---
> This patch was locally tested using the reproducer and .config file 
> generated by syzbot.
> 
>  net/can/af_can.c | 19 ++++++++++++++-----
>  1 file changed, 14 insertions(+), 5 deletions(-)
> 
> diff --git a/net/can/af_can.c b/net/can/af_can.c
> index ea29a6d97ef5..1b9f2e50f065 100644
> --- a/net/can/af_can.c
> +++ b/net/can/af_can.c
> @@ -694,16 +694,25 @@ static int canfd_rcv(struct sk_buff *skb, struct net_device *dev,

Can you create a similar patch for "can_rcv()"?

>  {
>  	struct canfd_frame *cfd = (struct canfd_frame *)skb->data;
>  
> -	if (unlikely(dev->type != ARPHRD_CAN || skb->len != CANFD_MTU ||
> -		     cfd->len > CANFD_MAX_DLEN)) {
> -		pr_warn_once("PF_CAN: dropped non conform CAN FD skbuf: dev type %d, len %d, datalen %d\n",
> +	if (unlikely(dev->type != ARPHRD_CAN || skb->len != CANFD_MTU)) {
> +		pr_warn_once("PF_CAN: dropped non conform CAN FD skbuff: dev type %d, len %d\n",
> +			     dev->type, skb->len);
> +		goto free_skb;
> +	}
> +
> +	// This check is made separately since cfd->len would be uninitialized if skb->len = 0.

Please don't use C++ comment style in the kernel.

> +	else if (unlikely(cfd->len > CANFD_MAX_DLEN)) {

Please move the "else" right after the closing curly bracket: "} else if () {"
or convert it into an "if () {"

> +		pr_warn_once("PF_CAN: dropped non conform CAN FD skbuff: dev type %d, len %d, datalen %d\n",
>  			     dev->type, skb->len, cfd->len);
> -		kfree_skb(skb);
> -		return NET_RX_DROP;
> +		goto free_skb;
>  	}
>  
>  	can_receive(skb, dev);
>  	return NET_RX_SUCCESS;
> +
> +free_skb:
> +	kfree_skb(skb);
> +	return NET_RX_DROP;
>  }
>  
>  /* af_can protocol functions */
> 

regards,
Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-11-02  7:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  3:13 Anant Thazhemadam
2020-11-02  7:10 ` Marc Kleine-Budde [this message]
2020-11-02  7:44   ` Anant Thazhemadam
2020-11-02  8:28     ` 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=1817819d-3aeb-8034-a4ec-7c70040b0cf0@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=anant.thazhemadam@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --cc=syzbot+9bcb0c9409066696d3aa@syzkaller.appspotmail.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

all inboxes | Powered by JetHome®