From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netdev@vger.kernel.org
Subject: Re: [iproute PATCH v3 2/5] nstat: Fix for potential NULL pointer dereference
Date: Mon, 21 Aug 2017 17:19:45 -0700 [thread overview]
Message-ID: <20170821171945.3d1f5a71@xeon-e3> (raw)
In-Reply-To: <20170821100308.24854-3-phil@nwl.cc>
On Mon, 21 Aug 2017 12:03:05 +0200
Phil Sutter <phil@nwl.cc> wrote:
> If the string at 'p' contains neither space not newline, 'p' will become
> NULL. Make sure this isn't the case before dereferencing it.
>
> Signed-off-by: Phil Sutter <phil@nwl.cc>
> ---
> Changes since v2:
> - Call abort() if 'p' becomes NULL.
> ---
> misc/nstat.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/misc/nstat.c b/misc/nstat.c
> index a4dd405d43a93..56e9367e99736 100644
> --- a/misc/nstat.c
> +++ b/misc/nstat.c
> @@ -217,6 +217,8 @@ static void load_ugly_table(FILE *fp)
> n->next = db;
> db = n;
> p = next;
> + if (!p)
> + abort();
> }
> n = db;
> if (fgets(buf, sizeof(buf), fp) == NULL)
This doesn't do anything better than just dereferencing NULL.
In either case program crashes with no useful information to user.
Not applying this.
next prev parent reply other threads:[~2017-08-22 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 10:03 [iproute PATCH v3 0/5] Covscan: Fix potential NULL pointer dereferences Phil Sutter
2017-08-21 10:03 ` [iproute PATCH v3 1/5] ifstat, nstat: Check fdopen() return value Phil Sutter
2017-08-21 10:03 ` [iproute PATCH v3 2/5] nstat: Fix for potential NULL pointer dereference Phil Sutter
2017-08-22 0:19 ` Stephen Hemminger [this message]
2017-08-21 10:03 ` [iproute PATCH v3 3/5] tc/q_netem: Don't dereference possibly NULL pointer Phil Sutter
2017-08-21 10:03 ` [iproute PATCH v3 4/5] tc/tc_filter: Make sure filter name is not empty Phil Sutter
2017-08-21 14:53 ` David Laight
2017-08-21 17:15 ` Phil Sutter
2017-08-21 10:03 ` [iproute PATCH v3 5/5] tipc/bearer: Prevent NULL pointer dereference Phil Sutter
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=20170821171945.3d1f5a71@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
/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).