From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kees@kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <horms@kernel.org>,
<idosch@nvidia.com>, <kuba@kernel.org>, <kuniyu@amazon.com>,
<linux-hardening@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>, <petrm@nvidia.com>
Subject: Re: [PATCH] rtnetlink: do_setlink: Use true struct sockaddr
Date: Tue, 17 Dec 2024 11:41:56 +0900 [thread overview]
Message-ID: <20241217024156.43328-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20241217020441.work.066-kees@kernel.org>
From: Kees Cook <kees@kernel.org>
Date: Mon, 16 Dec 2024 18:04:45 -0800
> Instead of a heap allocation use a stack allocated struct sockaddr, as
> dev_set_mac_address_user() is the consumer (which uses a classic
> struct sockaddr).
I remember Eric's feedback was to keep using heap instead of stack
because rtnl_newlink() path already uses too much on stack.
> Cap the copy to the minimum address size between
> the incoming address and the traditional sa_data field itself.
>
> Putting "sa" on the stack means it will get a reused stack slot since
> it is smaller than other existing single-scope stack variables (like
> the vfinfo array).
>
> Signed-off-by: Kees Cook <kees@kernel.org>
> ---
> Cc: Eric Dumazet <edumazet@google.com>
> Cc: "David S. Miller" <davem@davemloft.net>
> Cc: Jakub Kicinski <kuba@kernel.org>
> Cc: Paolo Abeni <pabeni@redhat.com>
> Cc: Ido Schimmel <idosch@nvidia.com>
> Cc: Petr Machata <petrm@nvidia.com>
> Cc: netdev@vger.kernel.org
> ---
> net/core/rtnetlink.c | 22 +++++++---------------
> 1 file changed, 7 insertions(+), 15 deletions(-)
>
> diff --git a/net/core/rtnetlink.c b/net/core/rtnetlink.c
> index ab5f201bf0ab..6da0edc0870d 100644
> --- a/net/core/rtnetlink.c
> +++ b/net/core/rtnetlink.c
> @@ -3048,21 +3048,13 @@ static int do_setlink(const struct sk_buff *skb, struct net_device *dev,
> }
>
> if (tb[IFLA_ADDRESS]) {
> - struct sockaddr *sa;
> - int len;
> -
> - len = sizeof(sa_family_t) + max_t(size_t, dev->addr_len,
> - sizeof(*sa));
> - sa = kmalloc(len, GFP_KERNEL);
> - if (!sa) {
> - err = -ENOMEM;
> - goto errout;
> - }
> - sa->sa_family = dev->type;
> - memcpy(sa->sa_data, nla_data(tb[IFLA_ADDRESS]),
> - dev->addr_len);
> - err = dev_set_mac_address_user(dev, sa, extack);
> - kfree(sa);
> + struct sockaddr sa = { };
> +
> + /* dev_set_mac_address_user() uses a true struct sockaddr. */
> + sa.sa_family = dev->type;
> + memcpy(sa.sa_data, nla_data(tb[IFLA_ADDRESS]),
> + min(dev->addr_len, sizeof(sa.sa_data_min)));
> + err = dev_set_mac_address_user(dev, &sa, extack);
> if (err)
> goto errout;
> status |= DO_SETLINK_MODIFIED;
> --
> 2.34.1
next prev parent reply other threads:[~2024-12-17 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 2:04 [PATCH] rtnetlink: do_setlink: Use true struct sockaddr Kees Cook
2024-12-17 2:41 ` Kuniyuki Iwashima [this message]
2024-12-17 7:53 ` Kees Cook
2024-12-17 8:03 ` Kuniyuki Iwashima
2024-12-17 9:33 ` Kees Cook
2024-12-17 8:03 ` ericnetdev dumazet
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=20241217024156.43328-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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).