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]

Date:   Wed, 14 Feb 2018 18:14:23 +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 5:53 PM, Santosh Shilimkar
<santosh.shilimkar@...cle.com> wrote:
>>> On 12/30/17 1:17 AM, syzbot wrote:
>>>>
>>>>
>>>> Hello,
>>>>
>>>> syzkaller hit the following crash on
>>>> fba961ab29e5ffb055592442808bb0f7962e05da
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
>>>> compiler: gcc (GCC) 7.1.1 20170620
>>>> .config is attached
>>>> Raw console output is attached.
>>>> Unfortunately, I don't have any reproducer for this bug yet.
>>>>
>>>>
>>>> IMPORTANT: if you fix the bug, please add the following tag to the
>>>> commit:
>>>> Reported-by: syzbot+93a5839deb355537440f@...kaller.appspotmail.com
>>>
>>>
>>>
>>> Posted a fix[1] for above issue. Didn't test it but looks straight
>>> forward.
>>
>>
>>
>> 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.