Re: net/dccp: use-after-free in dccp_feat_activate_values

On Fri, 2017-03-03 at 16:06 +0100, Dmitry Vyukov wrote:

Something that compiles is definitely better :)
Reapplied.

Just to be clear : This is not the proper patch. This only reduces the
race.

bh_lock_sock() does not prevent a user process from owning the socket.

We need another protection, probably RCU based, or another spinlock
protecting the fields needed at SYNACK generation.