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
| ||
|
Date: Mon, 14 Nov 2022 11:20:06 -0800 From: Richard Cochran <richardcochran@...il.com> To: syzbot <syzbot+0f89bd13eaceccc0e126@...kaller.appspotmail.com> Cc: casey@...aufler-ca.com, jmorris@...ei.org, linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, netdev@...r.kernel.org, paul@...l-moore.com, serge@...lyn.com, syzkaller-bugs@...glegroups.com Subject: Re: [syzbot] BUG: unable to handle kernel NULL pointer dereference in smack_inode_permission On Sun, Nov 13, 2022 at 04:05:47PM -0800, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 56751c56c2a2 Merge branch 'for-next/fixes' into for-kernelci > git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci > console output: https://syzkaller.appspot.com/x/log.txt?x=11fc8b0e880000 > kernel config: https://syzkaller.appspot.com/x/.config?x=606e57fd25c5c6cc > dashboard link: https://syzkaller.appspot.com/bug?extid=0f89bd13eaceccc0e126 > compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2 > userspace arch: arm64 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10a691fa880000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1733c5b9880000 > > Downloadable assets: > disk image: https://storage.googleapis.com/syzbot-assets/cf4668c75dea/disk-56751c56.raw.xz > vmlinux: https://storage.googleapis.com/syzbot-assets/e1ef82e91ef7/vmlinux-56751c56.xz > kernel image: https://storage.googleapis.com/syzbot-assets/3dabe076170f/Image-56751c56.gz.xz > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+0f89bd13eaceccc0e126@...kaller.appspotmail.com Why was this email addressed to me? Thanks, Richard
Powered by blists - more mailing lists