[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190701.113247.31622102771370431.davem@davemloft.net>
Date: Mon, 01 Jul 2019 11:32:47 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: mcroce@...hat.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH net v2] ipv4: don't set IPv6 only flags to IPv4
addresses
From: Matteo Croce <mcroce@...hat.com>
Date: Mon, 1 Jul 2019 19:01:55 +0200
> Avoid the situation where an IPV6 only flag is applied to an IPv4 address:
>
> # ip addr add 192.0.2.1/24 dev dummy0 nodad home mngtmpaddr noprefixroute
> # ip -4 addr show dev dummy0
> 2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
> inet 192.0.2.1/24 scope global noprefixroute dummy0
> valid_lft forever preferred_lft forever
>
> Or worse, by sending a malicious netlink command:
>
> # ip -4 addr show dev dummy0
> 2: dummy0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
> inet 192.0.2.1/24 scope global nodad optimistic dadfailed home tentative mngtmpaddr noprefixroute stable-privacy dummy0
> valid_lft forever preferred_lft forever
>
> Signed-off-by: Matteo Croce <mcroce@...hat.com>
Applied and queued up for -stable, thanks Matteo.
Powered by blists - more mailing lists