From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Michal Kubecek <mkubecek@suse.cz>
Subject: Re: [PATCH net-next] net: ethtool: fix NULL pointer dereference in stats_prepare_data()
Date: Wed, 25 Jan 2023 02:45:17 +0200 [thread overview]
Message-ID: <20230125004517.74c7ssj47zykciuv@skbuf> (raw)
In-Reply-To: <20230124162347.48bdae92@kernel.org>
On Tue, Jan 24, 2023 at 04:23:47PM -0800, Jakub Kicinski wrote:
> On Tue, 24 Jan 2023 13:08:01 +0200 Vladimir Oltean wrote:
> > In the following call path:
> >
> > ethnl_default_dumpit
> > -> ethnl_default_dump_one
> > -> ctx->ops->prepare_data
> > -> stats_prepare_data
> >
> > struct genl_info *info will be passed as NULL, and stats_prepare_data()
> > dereferences it while getting the extended ack pointer.
> >
> > To avoid that, just set the extack to NULL if "info" is NULL, since the
> > netlink extack handling messages know how to deal with that.
> >
> > The pattern "info ? info->extack : NULL" is present in quite a few other
> > "prepare_data" implementations, so it's clear that it's a more general
> > problem to be dealt with at a higher level, but the code should have at
> > least adhered to the current conventions to avoid the NULL dereference.
>
> Choose one:
> - you disagree with my comment on the report
> - you don't think that we should mix the immediate fix with the
> structural change
> - you agree but "don't have the time" to fix this properly
Yeah, sorry, I shouldn't have left your question unanswered ("should we make
a fake struct genl_info * to pass here?") - but I don't think I'm qualified
enough to have an opinion, either. Whereas the immediate fix is neutral
enough to not be controversial, or so I thought.
The problem is not so much "the time to fix this properly", but rather,
I'm not even sure how to trigger the ethtool dumpit() code...
next prev parent reply other threads:[~2023-01-25 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 11:08 [PATCH net-next] net: ethtool: fix NULL pointer dereference in stats_prepare_data() Vladimir Oltean
2023-01-24 12:28 ` Leon Romanovsky
2023-01-25 0:23 ` Jakub Kicinski
2023-01-25 0:45 ` Vladimir Oltean [this message]
2023-01-25 0:52 ` Jakub Kicinski
2023-01-25 0:53 ` Vladimir Oltean
2023-01-25 1:17 ` Jakub Kicinski
2023-01-25 10:00 ` patchwork-bot+netdevbpf
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=20230125004517.74c7ssj47zykciuv@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).