netdev - Re: [syzbot] [crypto?] general protection fault in shash_async

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]

Date: Wed, 26 Jul 2023 11:46:42 +0200
From: Aleksandr Nogikh <nogikh@...gle.com>
To: syzbot <syzbot+0bc501b7bf9e1bc09958@...kaller.appspotmail.com>
Cc: alexander.deucher@....com, davem@...emloft.net, dhowells@...hat.com, 
	herbert@...dor.apana.org.au, linux-crypto@...r.kernel.org, 
	linux-kernel@...r.kernel.org, mario.limonciello@....com, 
	netdev@...r.kernel.org, pabeni@...hat.com, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [crypto?] general protection fault in shash_async_update

On Wed, Jul 26, 2023 at 1:32 AM syzbot
<syzbot+0bc501b7bf9e1bc09958@...kaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 30c3d3b70aba2464ee8c91025e91428f92464077
> Author: Mario Limonciello <mario.limonciello@....com>
> Date:   Tue May 30 16:57:59 2023 +0000
>
>     drm/amd: Disallow s0ix without BIOS support again
>
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=122e2c31a80000
> start commit:   [unknown]
> git tree:       net-next
> kernel config:  https://syzkaller.appspot.com/x/.config?x=526f919910d4a671
> dashboard link: https://syzkaller.appspot.com/bug?extid=0bc501b7bf9e1bc09958
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13f71275280000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11081055280000
>
> If the result looks correct, please mark the issue as fixed by replying with:

No, that's unlikely.

>
> #syz fix: drm/amd: Disallow s0ix without BIOS support again
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>