From: Miquel Raynal <miquel.raynal@bootlin.com>
To: 慕冬亮 <dzm91@hust.edu.cn>
Cc: "denis kirjanov" <dkirjanov@suse.de>,
"alexander aring" <alex.aring@gmail.com>,
"stefan schmidt" <stefan@datenfreihafen.org>,
"david s. miller" <davem@davemloft.net>,
"eric dumazet" <edumazet@google.com>,
"jakub kicinski" <kuba@kernel.org>,
"paolo abeni" <pabeni@redhat.com>,
syzbot+bd85b31816913a32e473@syzkaller.appspotmail.com,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: ieee802154: fix a null pointer in nl802154_trigger_scan
Date: Tue, 7 Mar 2023 10:34:02 +0100 [thread overview]
Message-ID: <20230307103402.4c15d223@xps-13> (raw)
In-Reply-To: <2b209456.234a2.186bb608224.Coremail.dzm91@hust.edu.cn>
Hi 慕冬亮,
dzm91@hust.edu.cn wrote on Tue, 7 Mar 2023 17:21:49 +0800 (GMT+08:00):
> > -----原始邮件-----
> > 发件人: "Miquel Raynal" <miquel.raynal@bootlin.com>
> > 发送时间: 2023-03-07 17:09:03 (星期二)
> > 收件人: "Denis Kirjanov" <dkirjanov@suse.de>
> > 抄送: "Dongliang Mu" <dzm91@hust.edu.cn>, "Alexander Aring" <alex.aring@gmail.com>, "Stefan Schmidt" <stefan@datenfreihafen.org>, "David
> > S. Miller" <davem@davemloft.net>, "Eric Dumazet" <edumazet@google.com>, "Jakub
> > Kicinski" <kuba@kernel.org>, "Paolo Abeni" <pabeni@redhat.com>, syzbot+bd85b31816913a32e473@syzkaller.appspotmail.com, linux-wpan@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
> > 主题: Re: [PATCH] net: ieee802154: fix a null pointer in nl802154_trigger_scan
> >
> > Hello,
> >
> > dkirjanov@suse.de wrote on Tue, 7 Mar 2023 11:43:46 +0300:
> >
> > > On 3/7/23 10:30, Dongliang Mu wrote:
> > > > There is a null pointer dereference if NL802154_ATTR_SCAN_TYPE is
> > > > not set by the user.
> > > >
> > > > Fix this by adding a null pointer check.
> >
> > Thanks for the patch! This has been fixed already:
> > https://lore.kernel.org/linux-wpan/20230301154450.547716-1-miquel.raynal@bootlin.com/T/#u
>
> Oh, I see. Thanks for your reply.
>
> A small issue: should we still check !nla_get_u8(info->attrs[NL802154_ATTR_SCAN_TYPE])?
Isn't it already handled? There is a switch case over it with a default
statement to handle unsupported scan types.
> > > > Reported-and-tested-by: syzbot+bd85b31816913a32e473@syzkaller.appspotmail.com
> >
> > Just for reference, this tag shall not be used:
> >
> > "Please do not use combined tags, e.g.
> > ``Reported-and-tested-by``"
> > Documentation/process/maintainer-tip.rst
> >
>
> Okay. This is suggested by Syzbot. I will use separate tags in the future.
>
> > > > Signed-off-by: Dongliang Mu <dzm91@hust.edu.cn>
> > >
> > > Please add a Fixes: tag
> > >
> > > > ---
> > > > net/ieee802154/nl802154.c | 3 ++-
> > > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/net/ieee802154/nl802154.c b/net/ieee802154/nl802154.c
> > > > index 2215f576ee37..1cf00cffd63f 100644
> > > > --- a/net/ieee802154/nl802154.c
> > > > +++ b/net/ieee802154/nl802154.c
> > > > @@ -1412,7 +1412,8 @@ static int nl802154_trigger_scan(struct sk_buff *skb, struct genl_info *info)
> > > > return -EOPNOTSUPP;
> > > > }
> > > >
> > > > - if (!nla_get_u8(info->attrs[NL802154_ATTR_SCAN_TYPE])) {
> > > > + if (!info->attrs[NL802154_ATTR_SCAN_TYPE] ||
> > > > + !nla_get_u8(info->attrs[NL802154_ATTR_SCAN_TYPE])) {
> > > > NL_SET_ERR_MSG(info->extack, "Malformed request, missing scan type");
> > > > return -EINVAL;
> > > > }
> >
> >
> > Thanks,
> > Miquèl
>
>
> --
> Best regards,
> Dongliang Mu
Thanks,
Miquèl
next prev parent reply other threads:[~2023-03-07 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 7:30 [PATCH] net: ieee802154: fix a null pointer in nl802154_trigger_scan Dongliang Mu
2023-03-07 8:43 ` Denis Kirjanov
2023-03-07 9:09 ` Miquel Raynal
2023-03-07 9:21 ` 慕冬亮
2023-03-07 9:34 ` Miquel Raynal [this message]
2023-03-07 9:09 ` 慕冬亮
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=20230307103402.4c15d223@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=dkirjanov@suse.de \
--cc=dzm91@hust.edu.cn \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.org \
--cc=syzbot+bd85b31816913a32e473@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;
as well as URLs for NNTP newsgroup(s).