linux-kernel - Re: BUG: unable to handle kernel paging request in ipcget

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] [day] [month] [year] [list]

Date:   Sun, 7 Jan 2018 12:19:27 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     Manfred Spraul <manfred@...orfullife.com>,
        syzbot 
        <bot+362ae63b121c06066d2b6e1385d38efecbeca4f6@...kaller.appspotmail.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Davidlohr Bueso <dave@...olabs.net>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Guillaume Knispel <guillaume.knispel@...ersonicimagine.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Michal Hocko <mhocko@...e.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        syzkaller-bugs@...glegroups.com,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: BUG: unable to handle kernel paging request in ipcget

On Tue, Jan 2, 2018 at 7:16 PM, Kees Cook <keescook@...omium.org> wrote:
> On Sat, Dec 23, 2017 at 2:07 AM, Dmitry Vyukov <dvyukov@...gle.com> wrote:
>> On Sat, Dec 23, 2017 at 10:59 AM, Manfred Spraul
>> <manfred@...orfullife.com> wrote:
>>> Hi,
>>>
>>> On 12/23/2017 08:33 AM, syzbot wrote:
>>>>
>>>> Hello,
>>>>
>>>> syzkaller hit the following crash on
>>>> 6084b576dca2e898f5c101baef151f7bfdbb606d
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-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.
>>>>
>>> Is one of the recent issues reproducible?
>>
>> Which one do you mean?
>> syzbot always provides up-to-date status of reproducers for all reported bugs.
>>
>>> Either something is wrong with the faster ipc_get, or the improved ipc_get
>>> makes issues in other areas visible.
>
> Was this report related to the recent set of kmalloc-1024 false positives?


That's possible. It happened only twice and is unexplainable (right?). Let's do:

#syz fix: crypto: pcrypt - fix freeing pcrypt instances

and see if this happens again after the commit lands.