linux-kernel - Re: [syzbot] [audit?] BUG: unable to handle kernel NULL pointer dereference in kauditd_hold

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] [day] [month] [year] [list]

Message-ID: <CAHC9VhTY47hMxCYbU08aj0VGoPLQviL_6rGfTPyMDe8K36wPkQ@mail.gmail.com>
Date: Mon, 13 May 2024 10:59:32 -0400
From: Paul Moore <paul@...l-moore.com>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: syzbot <syzbot+8ffdaad8822cadf6ff4e@...kaller.appspotmail.com>, 
	audit@...r.kernel.org, eparis@...hat.com, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [audit?] BUG: unable to handle kernel NULL pointer
 dereference in kauditd_hold_skb

On Fri, May 10, 2024 at 3:01 AM Aleksandr Nogikh <nogikh@...gle.com> wrote:
> On Fri, May 10, 2024 at 1:27 AM Paul Moore <paul@...l-moore.com> wrote:
> >
> > On Thu, May 9, 2024 at 4:14 AM syzbot
> > <syzbot+8ffdaad8822cadf6ff4e@...kaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    6d7ddd805123 Merge tag 'soc-fixes-6.9-3' of git://gitkern..
> > > git tree:       upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=10c901b8980000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=758bb5b8f724c7ba
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=8ffdaad8822cadf6ff4e
> > > compiler:       arm-linux-gnueabi-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> > > userspace arch: arm
> > > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=17ed19b8980000
> >
> > Is syzbot no longer providing reproducers in C?  I see the syzbot
> > reproducer but no vanilla C code ...
>
> Syzbot still provides them, but in this particular case when syzbot
> tried to translate the .syz repro to C, it was unable to reproduce the
> problem anymore. So it didn't report it. It usually doesn't stay too
> long like this, in some time it will find a working C reproducer.

Thanks for the explanation.  This failure looks odd enough that I'll
wait for the C reproducer to spend any more time on it.

-- 
paul-moore.com