netdev - Re: pull request (net): ipsec 2018-01-11

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]

Date:   Fri, 12 Jan 2018 10:33:10 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     steffen.klassert@...unet.com
Cc:     herbert@...dor.apana.org.au, netdev@...r.kernel.org
Subject: Re: pull request (net): ipsec 2018-01-11

From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Thu, 11 Jan 2018 12:37:35 +0100

> 1) Don't allow to change the encap type on state updates.
>    The encap type is set on state initialization and
>    should not change anymore. From Herbert Xu.
> 
> 2) Skip dead policies when rehashing to fix a
>    slab-out-of-bounds bug in xfrm_hash_rebuild.
>    From Florian Westphal.
> 
> 3) Two buffer overread fixes in pfkey.
>    From Eric Biggers.
> 
> 4) Fix rcu usage in xfrm_get_type_offload,
>    request_module can sleep, so can't be used
>    under rcu_read_lock. From Sabrina Dubroca.
> 
> 5) Fix an uninitialized lock in xfrm_trans_queue.
>    Use __skb_queue_tail instead of skb_queue_tail
>    in xfrm_trans_queue as we don't need the lock.
>    From Herbert Xu.
> 
> 6) Currently it is possible to create an xfrm state with an
>    unknown encap type in ESP IPv4. Fix this by returning an
>    error on unknown encap types. Also from Herbert Xu.
> 
> 7) Fix sleeping inside a spinlock in xfrm_policy_cache_flush.
>    From Florian Westphal.
> 
> 8) Fix ESP GRO when the headers not fully in the linear part
>    of the skb. We need to pull before we can access them.
> 
> 9) Fix a skb leak on error in key_notify_policy.
> 
> 10) Fix a race in the xdst pcpu cache, we need to
>     run the resolver routines with bottom halfes
>     off like the old flowcache did.
> 
> Please pull or let me know if there are problems.

Pulled, thanks Steffen.