From: Dan Carpenter <dan.carpenter@oracle.com>
To: Xue Liu <liuxuenetmail@gmail.com>
Cc: "alex. aring" <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
"David S. Miller" <davem@davemloft.net>,
linux-wpan - ML <linux-wpan@vger.kernel.org>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] ieee802154: mcr20a: read out of bounds in mcr20a_set_channel()
Date: Thu, 30 Aug 2018 10:54:21 +0300 [thread overview]
Message-ID: <20180830075421.czsb5pa5b2vygp2m@mwanda> (raw)
In-Reply-To: <CAJuUDwtjRi0HnR95uaFp4zviSC7Yrs68o8jsK1nY6jWu6909bg@mail.gmail.com>
On Wed, Aug 29, 2018 at 07:50:51PM +0200, Xue Liu wrote:
> Hello Dan,
>
>
> On Wed, 29 Aug 2018 at 16:49, Dan Carpenter <dan.carpenter@oracle.com>
> wrote:
>
> > The "channel" variable can be any u8 value. We need to make sure we
> > don't read outside of the PLL_INT[] or PLL_FRAC[] arrays.
> >
> I think the “channel” variable can not be any u8 value. This values is
> already checked before set_channel function is called.
> https://github.com/torvalds/linux/blob/master/net/ieee802154/nl802154.c#L978
Oh... Hm... I should have reviewed more carefully. This patch isn't
correct. But there may still be a bug. What Smatch is worried about is
the other call tree:
ieee802154_start_req() calls (struct ieee802154_mlme_ops)->start_req
-> mac802154_mlme_start_req()
-> mac802154_dev_set_page_channel()
-> drv_set_channel() calls local->ops->set_channel(&local->hw, page, channel);
-> mcr20a_set_channel()
So maybe we could move the check from nl802154_set_channel() to
drv_set_channel() so channel is checked on both call trees.
regards,
dan carpenter
prev parent reply other threads:[~2018-08-30 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 14:49 [PATCH] ieee802154: mcr20a: read out of bounds in mcr20a_set_channel() Dan Carpenter
[not found] ` <CAJuUDwtjRi0HnR95uaFp4zviSC7Yrs68o8jsK1nY6jWu6909bg@mail.gmail.com>
2018-08-30 7:54 ` Dan Carpenter [this message]
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=20180830075421.czsb5pa5b2vygp2m@mwanda \
--to=dan.carpenter@oracle.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=liuxuenetmail@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
/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