Netdev List
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@nvidia.com>
To: Quentin Armitage <quentin@armitage.org.uk>
Cc: David Ahern <dsahern@kernel.org>, netdev@vger.kernel.org
Subject: Re: net: parsing IFLA_INET_CONF broken since 7.1 if NLA_F_NESTED not set
Date: Mon, 14 Sep 2026 18:42:14 +0300	[thread overview]
Message-ID: <20260914154214.GA422548@shredder> (raw)
In-Reply-To: <20260914152721.GB391235@shredder>

On Mon, Sep 14, 2026 at 06:27:21PM +0300, Ido Schimmel wrote:
> On Mon, Sep 14, 2026 at 03:21:59PM +0100, Quentin Armitage wrote:
> > Commit fa8fca88714c - "ipv4: validate IPV4_DEVCONF attributes properly" changed
> > inet_validate_link_af() to call nla_parse_nested() rather than
> > nla_for_each_nested() for IFLA_INET_CONF. A side effect of this change is that
> > the code now checks that NLA_F_NESTED is set for IFLA_INET_CONF, and rejects the
> > message if it is not, whereas previously there was no check for NLA_F_NESTED
> > being set.
> > 
> > The consequence of this is that code which worked prior to Linux 7.1, albeit
> > erroneously not setting NLA_F_NESTED now fails.
> > 
> > In order to maintain backward compatibility, rather than calling
> > nla_parse_nested(), nla_parse_nested_deprecated() should be called, as it is
> > earlier in the function.
> 
> I don't think nla_parse_nested_deprecated() is safe. It will allow
> attributes exceeding the maximum type or with type 0, which can then
> crash in inet_set_link_af(). Can you try nla_parse_deprecated_strict()
> instead?
> 
> diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
> index a90be57c63be..4e0e153f504f 100644
> --- a/net/ipv4/devinet.c
> +++ b/net/ipv4/devinet.c
> @@ -2117,10 +2117,10 @@ static int inet_validate_link_af(const struct net_device *dev,
>  		return err;
>  
>  	if (tb[IFLA_INET_CONF]) {
> -		err = nla_parse_nested(nested_tb, IPV4_DEVCONF_MAX,
> -				       tb[IFLA_INET_CONF], inet_devconf_policy,
> -				       extack);
> -
> +		err = nla_parse_deprecated_strict(nested_tb, IPV4_DEVCONF_MAX,
> +						  nla_data(tb[IFLA_INET_CONF]),
> +						  nla_len(tb[IFLA_INET_CONF]),
> +						  inet_devconf_policy, extack);
>  		if (err < 0)
>  			return err;
>  	}

Actually, nla_parse() would be closer to what is currently in the tree
and should still fix the breakage:

diff --git a/net/ipv4/devinet.c b/net/ipv4/devinet.c
index a90be57c63be..1f747826542a 100644
--- a/net/ipv4/devinet.c
+++ b/net/ipv4/devinet.c
@@ -2117,10 +2117,10 @@ static int inet_validate_link_af(const struct net_device *dev,
 		return err;
 
 	if (tb[IFLA_INET_CONF]) {
-		err = nla_parse_nested(nested_tb, IPV4_DEVCONF_MAX,
-				       tb[IFLA_INET_CONF], inet_devconf_policy,
-				       extack);
-
+		err = nla_parse(nested_tb, IPV4_DEVCONF_MAX,
+				nla_data(tb[IFLA_INET_CONF]),
+				nla_len(tb[IFLA_INET_CONF]),
+				inet_devconf_policy, extack);
 		if (err < 0)
 			return err;
 	}


  reply	other threads:[~2026-09-14 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 14:21 net: parsing IFLA_INET_CONF broken since 7.1 if NLA_F_NESTED not set Quentin Armitage
2026-09-14 15:27 ` Ido Schimmel
2026-09-14 15:42   ` Ido Schimmel [this message]
2026-09-14 17:21 ` Jakub Kicinski
2026-09-14 17:43   ` Ido Schimmel
2026-09-14 17:51     ` Jakub Kicinski
2026-09-14 17:52     ` Quentin Armitage

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=20260914154214.GA422548@shredder \
    --to=idosch@nvidia.com \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=quentin@armitage.org.uk \
    /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