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

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: <s5h60at83c3.wl-tiwai@suse.de>
Date:   Thu, 02 Nov 2017 09:58:04 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     "Dmitry Vyukov" <dvyukov@...gle.com>
Cc:     "syzbot" 
        <bot+31681772ec7a18dde8d3f8caf475f361a89b9514@...kaller.appspotmail.com>,
        <alsa-devel@...a-project.org>, <syzkaller-bugs@...glegroups.com>,
        "Jaroslav Kysela" <perex@...ex.cz>,
        "LKML" <linux-kernel@...r.kernel.org>,
        "Mark Salyzyn" <salyzyn@...roid.com>
Subject: Re: BUG: unable to handle kernel paging request in snd_seq_oss_readq_puts

On Wed, 01 Nov 2017 20:49:10 +0100,
Takashi Iwai wrote:
> 
> On Wed, 01 Nov 2017 19:39:46 +0100,
> Dmitry Vyukov wrote:
> > 
> > On Wed, Nov 1, 2017 at 9:38 PM, syzbot
> > <bot+31681772ec7a18dde8d3f8caf475f361a89b9514@...kaller.appspotmail.com>
> > wrote:
> > > Hello,
> > >
> > > syzkaller hit the following crash on
> > > fc2e8b1a47c14b22c33eb087fca0db58e1f4ed0e
> > > 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.
> > > C reproducer is attached
> > > syzkaller reproducer is attached. See https://goo.gl/kgGztJ
> > > for information about syzkaller reproducers
> > 
> > This also happened on more recent commits, including upstream
> > 9c323bff13f92832e03657cabdd70d731408d621 (Oct 20):
> 
> Could you try the patch below with CONFIG_SND_DEBUG=y and see whether
> it catches any bad calls?  It's already in for-next branch for 4.15.

And now I remember that it's the exactly same bug Mark Salyzyn
reported sometime ago, msgid
 <20171006171731.88889-1-salyzyn@...roid.com>

So this is likely hitting an invalid page, if Mark's analysis is
correct.


thanks,

Takashi