linux-kernel - Re: KASAN: use-after-free Read in rds_find

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: <CACT4Y+aWVFEvVMihw2MBiMgYKMzup4O78c_HrByhRyF8-zfzpw@mail.gmail.com>
Date:   Wed, 14 Feb 2018 18:52:58 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Santosh Shilimkar <santosh.shilimkar@...cle.com>
Cc:     syzbot <syzbot+93a5839deb355537440f@...kaller.appspotmail.com>,
        linux-rdma@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        David Miller <davem@...emloft.net>,
        LKML <linux-kernel@...r.kernel.org>,
        netdev <netdev@...r.kernel.org>, rds-devel@....oracle.com
Subject: Re: KASAN: use-after-free Read in rds_find_bound

On Wed, Feb 14, 2018 at 6:35 PM, Santosh Shilimkar
<santosh.shilimkar@...cle.com> wrote:
>>>> Hi Santosh,
>>>>
>>>> What is that fix? You forgot to provide any link/reference. I also
>>>> don't see any patches from you at around that date...
>>>>
>>> Fix [1] was later not added since there was a still a race. Wanted to
>>> see if the issue re-appears after recent netns fix [2].
>>
>>
>>
>> We will not see if the bug re-appears or not until this bug is closed.
>> Please see this recent discussion about another rds bug:
>> https://groups.google.com/d/msg/syzkaller-bugs/3XjmOzr5jRU/g7pXIsY1BgAJ
>> In the current state syzbot will never report bugs in these functions
>> again.
>>
> OK. Can you close that one then in that case ?

Anybody can do this:

#syz fix: rds: tcp: use rds_destroy_pending() to synchronize
netns/module teardown and rds connection/workq management

syzbot provides full self-service, see first email and in particular this:
https://github.com/google/syzkaller/blob/master/docs/syzbot.md#communication-with-syzbot

Thanks