netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Thomas Graf <tgraf@suug.ch>, Jiri Pirko <jiri@resnulli.us>
Cc: 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 08:58:27 -0800	[thread overview]
Message-ID: <547606B3.3060808@gmail.com> (raw)
In-Reply-To: <cover.1417005245.git.tgraf@suug.ch>

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.

>
> diff --git a/drivers/net/bonding/bond_netlink.c b/drivers/net/bonding/bond_netlink.c
> index 3e6eebd..7b11243 100644
> --- a/drivers/net/bonding/bond_netlink.c
> +++ b/drivers/net/bonding/bond_netlink.c
> @@ -225,7 +225,12 @@ static int bond_changelink(struct net_device *bond_dev,
>
>                 bond_option_arp_ip_targets_clear(bond);
>                 nla_for_each_nested(attr, data[IFLA_BOND_ARP_IP_TARGET], rem) {
> -                       __be32 target = nla_get_be32(attr);
> +                       __be32 target;
> +
> +                       if (nla_len(attr) < sizeof(target))
> +                               return -EINVAL;
> +
> +                       target = nla_get_be32(attr);
>
>                         bond_opt_initval(&newval, (__force u64)target);
>                         err = __bond_opt_set(bond, BOND_OPT_ARP_TARGETS,

-- 
John Fastabend         Intel Corporation

  parent reply	other threads:[~2014-11-26 16:58 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 ` John Fastabend [this message]
2014-11-26 17:06   ` [PATCH 0/5 net] bridge: Fix missing Netlink message validations Thomas Graf
2014-11-26 17:25     ` John Fastabend
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=547606B3.3060808@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 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).