netdev - Re: [PATCH v2 net-next 0/2] kcm: fix two syzcaller issues

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180124.155445.1219599573440727295.davem@davemloft.net>
Date:   Wed, 24 Jan 2018 15:54:45 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     tom@...ntonium.net
Cc:     netdev@...r.kernel.org, rohit@...ntonium.net, jchapman@...alix.com,
        g.nault@...halink.fr
Subject: Re: [PATCH v2 net-next 0/2] kcm: fix two syzcaller issues

From: Tom Herbert <tom@...ntonium.net>
Date: Wed, 24 Jan 2018 12:35:39 -0800

> In this patch set:
> 
> - Don't allow attaching non-TCP or listener sockets to a KCM mux.
> - In kcm_attach Check if sk_user_data is already set. This is
>   under lock to avoid race conditions. More work is need to make
>   all of the users of sk_user_data to use the same locking.
> 
> - v2
>   Remove unncessary check for not PF_KCM in kcm_attach (suggested by
>   Guillaume Nault)

Series applied, thanks Tom.