From: John Fastabend <john.fastabend@gmail.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: Jiri Pirko <jiri@resnulli.us>,
davem@davemloft.net, stephen@networkplumber.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/5 net] bridge: Fix missing Netlink message validations
Date: Wed, 26 Nov 2014 09:25:49 -0800 [thread overview]
Message-ID: <54760D1D.3070201@gmail.com> (raw)
In-Reply-To: <20141126170610.GA2399@casper.infradead.org>
On 11/26/2014 09:06 AM, Thomas Graf wrote:
> On 11/26/14 at 08:58am, John Fastabend wrote:
>> On 11/26/2014 04:42 AM, Thomas Graf wrote:
>>> Adds various missing length checks in the bridging code for Netlink
>>> messages and corresponding attributes provided by user space.
>>>
>>> Thomas Graf (5):
>>> bridge: Validate IFLA_BRIDGE_FLAGS attribute length
>>> net: Validate IFLA_BRIDGE_MODE attribute length
>>> net: Check for presence of IFLA_AF_SPEC
>>> bridge: Add missing policy entry for IFLA_BRPORT_FAST_LEAVE
>>> bridge: Sanitize IFLA_EXT_MASK for AF_BRIDGE:RTM_GETLINK
>>>
>>> drivers/net/ethernet/emulex/benet/be_main.c | 5 +++++
>>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 5 +++++
>>> net/bridge/br_netlink.c | 1 +
>>> net/core/rtnetlink.c | 23 ++++++++++++++++++-----
>>> 4 files changed, 29 insertions(+), 5 deletions(-)
>>>
>>
>> +Jiri
>>
>> Looks like a miss in bond_netlink also? Seems like writing
>> a smatch or cocci check for this would be worthwhile.
>
> Thanks, I'll take a look.
>
> The cocci check is somewhat difficult as validation is often
> centralized and decoupled from actual access to implement atomic
> operations. I'll give it a try though.
>
Sounds good, if I get some time I could give it a try as well.
Also another missing one here or at least I'm not seeing it if its
there,
> --- a/net/ipv4/devinet.c
> +++ b/net/ipv4/devinet.c
> @@ -1687,8 +1687,11 @@ static int inet_set_link_af(struct net_device *dev, const struct nlattr *nla)
> BUG();
>
> if (tb[IFLA_INET_CONF]) {
> - nla_for_each_nested(a, tb[IFLA_INET_CONF], rem)
> + nla_for_each_nested(a, tb[IFLA_INET_CONF], rem) {
> + if (nla_len(a) < sizeof(u32))
> + return -EINVAL;
> ipv4_devconf_set(in_dev, nla_type(a), nla_get_u32(a));
> + }
> }
--
John Fastabend Intel Corporation
next prev parent reply other threads:[~2014-11-26 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 12:42 [PATCH 0/5 net] bridge: Fix missing Netlink message validations Thomas Graf
2014-11-26 12:42 ` [PATCH 1/5] bridge: Validate IFLA_BRIDGE_FLAGS attribute length Thomas Graf
2014-11-26 12:42 ` [PATCH 2/5] net: Validate IFLA_BRIDGE_MODE " Thomas Graf
2014-11-26 13:29 ` Jeff Kirsher
2014-11-26 16:42 ` John Fastabend
2014-11-26 12:42 ` [PATCH 3/5] net: Check for presence of IFLA_AF_SPEC Thomas Graf
2014-11-26 13:30 ` Jeff Kirsher
2014-11-26 12:42 ` [PATCH 4/5] bridge: Add missing policy entry for IFLA_BRPORT_FAST_LEAVE Thomas Graf
2014-11-26 12:42 ` [PATCH 5/5] bridge: Sanitize IFLA_EXT_MASK for AF_BRIDGE:RTM_GETLINK Thomas Graf
2014-11-26 16:58 ` [PATCH 0/5 net] bridge: Fix missing Netlink message validations John Fastabend
2014-11-26 17:06 ` Thomas Graf
2014-11-26 17:25 ` John Fastabend [this message]
2014-11-26 23:14 ` Thomas Graf
2014-11-29 17:51 ` John Fastabend
2014-11-26 20:29 ` David Miller
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=54760D1D.3070201@gmail.com \
--to=john.fastabend@gmail.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.