[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Fri, 03 Mar 2017 07:13:04 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: Cong Wang <xiyou.wangcong@...il.com>,
Andrey Konovalov <andreyknvl@...gle.com>,
Gerrit Renker <gerrit@....abdn.ac.uk>,
"David S. Miller" <davem@...emloft.net>, dccp@...r.kernel.org,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>
Subject: 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.
Powered by blists - more mailing lists