From: Tuo Li <islituo@gmail.com>
To: john.fastabend@gmail.com, kpsingh@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, baijiaju1990@gmail.com
Subject: [BUG] ipv6: possible null-pointer dereference in ip6_xmit()
Date: Tue, 10 Aug 2021 21:46:13 +0800 [thread overview]
Message-ID: <2c434d4d-934f-f8d2-7f1f-af085fcfad26@gmail.com> (raw)
Hello,
Our static analysis tool finds a possible null-pointer dereference in
ip6_output.c in Linux 5.14.0-rc3:
The variable n is checked in:
314: if (np)
This indicates that it can be NULL. If so, a null-pointer dereference
will occur
in the called function ip6_autoflowlabel() at Line 320:
252: if (!np->autoflowlabel_set)
I am not quite sure whether this possible null-pointer dereference is
real and how to fix it if it is real.
Any feedback would be appreciated, thanks!
Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
Best wishes,
Tuo Li
reply other threads:[~2021-08-10 13:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2c434d4d-934f-f8d2-7f1f-af085fcfad26@gmail.com \
--to=islituo@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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
all inboxes | Powered by JetHome®