netdev - Re: [PATCH net v2] rtnetlink: Disallow FDB configuration for non-Ethernet device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20181029.205329.2193085560727068930.davem@davemloft.net>
Date:   Mon, 29 Oct 2018 20:53:29 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...lanox.com
Cc:     netdev@...r.kernel.org, vyasevich@...il.com, dsahern@...il.com
Subject: Re: [PATCH net v2] rtnetlink: Disallow FDB configuration for
 non-Ethernet device

From: Ido Schimmel <idosch@...lanox.com>
Date: Mon, 29 Oct 2018 20:36:43 +0000

> When an FDB entry is configured, the address is validated to have the
> length of an Ethernet address, but the device for which the address is
> configured can be of any type.
> 
> The above can result in the use of uninitialized memory when the address
> is later compared against existing addresses since 'dev->addr_len' is
> used and it may be greater than ETH_ALEN, as with ip6tnl devices.
> 
> Fix this by making sure that FDB entries are only configured for
> Ethernet devices.
 ...
> v2:
> * Make error message more specific (David)
> 
> Fixes: 090096bf3db1 ("net: generic fdb support for drivers without ndo_fdb_<op>")
> Signed-off-by: Ido Schimmel <idosch@...lanox.com>
> Reported-and-tested-by: syzbot+3a288d5f5530b901310e@...kaller.appspotmail.com
> Reported-and-tested-by: syzbot+d53ab4e92a1db04110ff@...kaller.appspotmail.com
> Cc: Vlad Yasevich <vyasevich@...il.com>
> Cc: David Ahern <dsahern@...il.com>

Applied and queued up for -stable, thanks.