From: walter harms <wharms@bfs.de>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
alan@linux.intel.com, hessu@hes.iki.fi,
martin.blumenstingl@googlemail.com, linux-hams@vger.kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net 1/3] net: validate variable length ll headers
Date: Sat, 05 Mar 2016 10:22:16 +0100 [thread overview]
Message-ID: <56DAA548.9040303@bfs.de> (raw)
In-Reply-To: <1457124257-31486-2-git-send-email-willemdebruijn.kernel@gmail.com>
Am 04.03.2016 21:44, schrieb Willem de Bruijn:
> From: Willem de Bruijn <willemb@google.com>
>
> Netdevice parameter hard_header_len is variously interpreted both as
> an upper and lower bound on link layer header length. The field is
> used as upper bound when reserving room at allocation, as lower bound
> when validating user input in PF_PACKET.
>
> Clarify the definition to be maximum header length. For validation
> of untrusted headers, add an optional validate member to header_ops.
>
> Allow bypassing of validation by passing CAP_SYS_RAWIO, for instance
> for deliberate testing of corrupt input. In this case, pad trailing
> bytes, as some device drivers expect completely initialized headers.
>
> See also http://comments.gmane.org/gmane.linux.network/401064
>
> Signed-off-by: Willem de Bruijn <willemb@google.com>
> ---
> include/linux/netdevice.h | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 5440b7b..6d1d8f4 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -267,6 +267,7 @@ struct header_ops {
> void (*cache_update)(struct hh_cache *hh,
> const struct net_device *dev,
> const unsigned char *haddr);
> + bool (*validate)(const char *ll_header, unsigned int len);
> };
>
> /* These flag bits are private to the generic network queueing
> @@ -1420,8 +1421,7 @@ enum netdev_priv_flags {
> * @dma: DMA channel
> * @mtu: Interface MTU value
> * @type: Interface hardware type
> - * @hard_header_len: Hardware header length, which means that this is the
> - * minimum size of a packet.
> + * @hard_header_len: Maximum hardware header length.
> *
> * @needed_headroom: Extra headroom the hardware may need, but not in all
> * cases can this be guaranteed
> @@ -2627,6 +2627,24 @@ static inline int dev_parse_header(const struct sk_buff *skb,
> return dev->header_ops->parse(skb, haddr);
> }
>
> +/* ll_header must have at least hard_header_len allocated */
> +static inline bool dev_validate_header(const struct net_device *dev,
> + char *ll_header, int len)
> +{
> + if (likely(len >= dev->hard_header_len))
> + return true;
> +
> + if (capable(CAP_SYS_RAWIO)) {
> + memset(ll_header + len, 0, dev->hard_header_len - len);
> + return true;
> + }
> +
> + if (dev->header_ops && dev->header_ops->validate)
> + return dev->header_ops->validate(ll_header, len);
> +
> + return false;
> +}
> +
you could use
real_len=dev->hard_header_len-len;
if (real_len < 0)
...
if (capable(CAP_SYS_RAWIO))
memset(ll_header + len, 0,real_len);
..
IMHO that makes the code more clear.
re,
wh
> typedef int gifconf_func_t(struct net_device * dev, char __user * bufptr, int len);
> int register_gifconf(unsigned int family, gifconf_func_t *gifconf);
> static inline int unregister_gifconf(unsigned int family)
next prev parent reply other threads:[~2016-03-05 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 20:44 [PATCH net 0/3] validate variable length ll headers Willem de Bruijn
2016-03-04 20:44 ` [PATCH net 1/3] net: " Willem de Bruijn
2016-03-05 9:22 ` walter harms [this message]
2016-03-04 20:44 ` [PATCH net 2/3] packet: " Willem de Bruijn
2016-03-07 17:38 ` Willem de Bruijn
2016-03-04 20:44 ` [PATCH net 3/3] ax25: add link layer header validation function Willem de Bruijn
2016-03-09 20:54 ` [PATCH net 0/3] validate variable length ll headers 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=56DAA548.9040303@bfs.de \
--to=wharms@bfs.de \
--cc=alan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=hessu@hes.iki.fi \
--cc=linux-hams@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.com \
/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).