[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 Apr 2017 01:29:19 +0800
From: Xin Long <lucien.xin@...il.com>
To: Andrey Konovalov <andreyknvl@...gle.com>
Cc: Vlad Yasevich <vyasevich@...il.com>,
Neil Horman <nhorman@...driver.com>,
"David S. Miller" <davem@...emloft.net>,
linux-sctp@...r.kernel.org, netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Eric Dumazet <edumazet@...gle.com>,
Kostya Serebryany <kcc@...gle.com>,
syzkaller <syzkaller@...glegroups.com>
Subject: Re: net/sctp: list double add warning in sctp_endpoint_add_asoc
On Tue, Apr 4, 2017 at 9:28 PM, Andrey Konovalov <andreyknvl@...gle.com> wrote:
> Hi,
>
> I've got the following error report while fuzzing the kernel with syzkaller.
>
> On commit a71c9a1c779f2499fb2afc0553e543f18aff6edf (4.11-rc5).
>
> A reproducer and .config are attached.
The script is pretty hard to reproduce the issue in my env.
But there seems a case to cause a use-after-free when out of snd_buf.
the case is like:
-----------
one thread: another thread:
sctp_rcv hold asoc (hold transport)
enqueue the chunk to backlog queue
[refcnt=2]
sctp_close free assoc
[refcnt=1]
sctp_sendmsg find asoc
but not hold it
out of snd_buf
hold asoc, schedule out
[refcnt = 2]
process backlog and put asoc/transport
[refcnt=1]
schedule in, put asoc
[refcnt=0] <--- destroyed
sctp_sendmsg continue
using asoc, panic
--------------------
Maybe we should check if asoc is dead already when schedule back
into sctp_sendmsg because of out of snd_buf.
Powered by blists - more mailing lists