[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62457d9f-0732-3886-0381-bbf5df738467@kernel.org>
Date: Tue, 2 Oct 2018 10:04:57 -0600
From: Shuah Khan <shuah@...nel.org>
To: syzbot <syzbot+bccc1fe10b70fadc78d0@...kaller.appspotmail.com>,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, syzkaller-bugs@...glegroups.com,
valentina.manea.m@...il.com
Cc: Shuah Khan <shuah@...nel.org>
Subject: Re: KASAN: slab-out-of-bounds Read in vhci_hub_control
On 09/04/2018 12:52 PM, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 420f51f4ab6b Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=126a6f0e400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=531a917630d2a492
> dashboard link: https://syzkaller.appspot.com/bug?extid=bccc1fe10b70fadc78d0
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=121caa46400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14ed8ab6400000
C producer doesn't reproduce the problem on 4.19-rc5. Does this C producer
depend on state of the machine? i.e what is the status of vhci_hcd - are
there any devices attached?
I can see the problem looking at the code and fix is easy. However, I would
like be able to reproduce it and verify the fix works. Also this would be a
good regression for the driver I could consider adding to selftests.
thanks,
-- Shuah
Powered by blists - more mailing lists