From: Leo Yan <leo.yan@linaro.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] bpf, libbpf: Smatch: Fix potential NULL pointer dereference
Date: Wed, 3 Jul 2019 19:46:25 +0800 [thread overview]
Message-ID: <20190703114625.GG6852@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <b834fba1-5b2c-4406-8275-1cf8383655e3@iogearbox.net>
On Wed, Jul 03, 2019 at 12:23:05PM +0200, Daniel Borkmann wrote:
> On 07/02/2019 12:25 PM, Leo Yan wrote:
> > Based on the following report from Smatch, fix the potential
> > NULL pointer dereference check.
> >
> > tools/lib/bpf/libbpf.c:3493
> > bpf_prog_load_xattr() warn: variable dereferenced before check 'attr'
> > (see line 3483)
> >
> > 3479 int bpf_prog_load_xattr(const struct bpf_prog_load_attr *attr,
> > 3480 struct bpf_object **pobj, int *prog_fd)
> > 3481 {
> > 3482 struct bpf_object_open_attr open_attr = {
> > 3483 .file = attr->file,
> > 3484 .prog_type = attr->prog_type,
> > ^^^^^^
> > 3485 };
> >
> > At the head of function, it directly access 'attr' without checking if
> > it's NULL pointer. This patch moves the values assignment after
> > validating 'attr' and 'attr->file'.
> >
> > Signed-off-by: Leo Yan <leo.yan@linaro.org>
> > ---
> > tools/lib/bpf/libbpf.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> > index 197b574406b3..809b633fa3d9 100644
> > --- a/tools/lib/bpf/libbpf.c
> > +++ b/tools/lib/bpf/libbpf.c
> > @@ -3479,10 +3479,7 @@ int bpf_prog_load(const char *file, enum bpf_prog_type type,
> > int bpf_prog_load_xattr(const struct bpf_prog_load_attr *attr,
> > struct bpf_object **pobj, int *prog_fd)
> > {
> > - struct bpf_object_open_attr open_attr = {
> > - .file = attr->file,
> > - .prog_type = attr->prog_type,
> > - };
>
> Applied, thanks! Fyi, I retained the zeroing of open_attr as otherwise if we ever
> extend struct bpf_object_open_attr in future, we'll easily miss this and pass in
> garbage to bpf_object__open_xattr().
Thanks for the info, Daniel.
I checked the link [1] and thanks for the improvement when applied this
patch.
Thanks,
Leo Yan
[1] https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/commit/?id=33bae185f74d49a0d7b1bfaafb8e959efce0f243
prev parent reply other threads:[~2019-07-03 11:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 10:25 [PATCH] bpf, libbpf: Smatch: Fix potential NULL pointer dereference Leo Yan
2019-07-02 15:34 ` Yonghong Song
2019-07-03 10:23 ` Daniel Borkmann
2019-07-03 11:46 ` Leo Yan [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=20190703114625.GG6852@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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