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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 5 Apr 2017 01:29:19 +0800
From:   Xin Long <>
To:     Andrey Konovalov <>
Cc:     Vlad Yasevich <>,
        Neil Horman <>,
        "David S. Miller" <>,, netdev <>,
        LKML <>,
        Marcelo Ricardo Leitner <>,
        Dmitry Vyukov <>,
        Eric Dumazet <>,
        Kostya Serebryany <>,
        syzkaller <>
Subject: Re: net/sctp: list double add warning in sctp_endpoint_add_asoc

On Tue, Apr 4, 2017 at 9:28 PM, Andrey Konovalov <> 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

sctp_close free assoc

sctp_sendmsg find asoc
but not hold it

out of snd_buf
hold asoc, schedule out
[refcnt = 2]

                                  process backlog and put asoc/transport

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