[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5j+n8XCAwsRzDRoaxRqDEH9byMB=6e5FxPW=1mrGoUzRRQ@mail.gmail.com>
Date: Wed, 7 Feb 2018 06:16:51 +1100
From: Kees Cook <keescook@...omium.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: syzbot <syzbot+c4dcac91687a29cbae15@...kaller.appspotmail.com>,
keun-o.park@...kmatter.ae, Laura Abbott <labbott@...hat.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>,
Mark Rutland <mark.rutland@....com>,
Ingo Molnar <mingo@...nel.org>, syzkaller-bugs@...glegroups.com
Subject: Re: WARNING: bad usercopy in put_cmsg
On Wed, Feb 7, 2018 at 4:33 AM, Dmitry Vyukov <dvyukov@...gle.com> wrote:
> On Tue, Feb 6, 2018 at 6:31 PM, syzbot
> <syzbot+c4dcac91687a29cbae15@...kaller.appspotmail.com> wrote:
>> Hello,
>>
>> syzbot hit the following crash on upstream commit
>> e237f98a9c134c3d600353f21e07db915516875b (Mon Feb 5 21:35:56 2018 +0000)
>> Merge tag 'xfs-4.16-merge-5' of
>> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
>>
>> So far this crash happened 8 times on net-next, upstream.
>> C reproducer is attached.
>> syzkaller reproducer is attached.
>> Raw console output is attached.
>> compiler: gcc (GCC) 7.1.1 20170620
>> .config is attached.
>
> #syz dup: WARNING in usercopy_warn
>
> Let's make that one the main copy, since Kees is already looking at it.
This one has a more descriptive subject, can we dup towards this one?
Whatever the case, yup, still working on it.
-Kees
--
Kees Cook
Pixel Security
Powered by blists - more mailing lists