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] [day] [month] [year] [list]
Date:   Tue, 26 Mar 2019 09:43:59 +0100
From:   Dmitry Vyukov <>
To:     syzbot <>
Cc:     Andrew Morton <>,
        Arnd Bergmann <>,
        Davidlohr Bueso <>,
        "Eric W. Biederman" <>,
        Greg Kroah-Hartman <>,
        LKML <>,
        Linux-MM <>,,
        manfred <>,
        syzkaller-bugs <>
Subject: Re: general protection fault in freeary

On Sun, Mar 24, 2019 at 7:51 PM syzbot
<> wrote:
> syzbot has bisected this bug to:
> commit 86f690e8bfd124c38940e7ad58875ef383003348
> Author: Greg Kroah-Hartman <>
> Date:   Thu Mar 29 12:15:13 2018 +0000
>      Merge tag 'stm-intel_th-for-greg-20180329' of
> git:// into char-misc-next
> bisection log:
> start commit:   74c4a24d Add linux-next specific files for 20181207
> git tree:       linux-next
> final crash:
> console output:
> kernel config:
> dashboard link:
> syz repro:
> Reported-by:
> Fixes: 86f690e8bfd1 ("Merge tag 'stm-intel_th-for-greg-20180329' of
> git:// into char-misc-next")
> For information about bisection process see:

Looking at the crash patterns in the bisection log it seems that this
is a stack overflow/corruption in wb_workfn. There are other reports
that suggest that simply causing OOM randomly corrupts kernel memory.
The semget is only an easy way to cause OOMs.
But since we now sandbox tests processes with sem sysctl and friends,
I think we can close this report.

#syz invalid

Though the kernel memory corruption on OOMs is still there.

Powered by blists - more mailing lists