Received-SPF: pass (google.com: domain of linux-kernel+bounces-177721-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Precedence: bulk
MIME-Version: 1.0
References: <000000000000f5f83206180101e7@google.com> <CAHC9VhSinu25_9evZZmLaiJL=R-LNOmB+Yz-3NtdMi5b+vQiRg@mail.gmail.com>
 <CANp29Y74qSm4_VTVT-j5n5kwpJaPk1zTMXPRO_xxWViXADUNeg@mail.gmail.com>
In-Reply-To: <CANp29Y74qSm4_VTVT-j5n5kwpJaPk1zTMXPRO_xxWViXADUNeg@mail.gmail.com>
From: Paul Moore <paul@paul-moore.com>
Date: Mon, 13 May 2024 10:59:32 -0400
Message-ID: <CAHC9VhTY47hMxCYbU08aj0VGoPLQviL_6rGfTPyMDe8K36wPkQ@mail.gmail.com>
Subject: Re: [syzbot] [audit?] BUG: unable to handle kernel NULL pointer
 dereference in kauditd_hold_skb
To: Aleksandr Nogikh <nogikh@google.com>
Cc: syzbot <syzbot+8ffdaad8822cadf6ff4e@syzkaller.appspotmail.com>, 
	audit@vger.kernel.org, eparis@redhat.com, linux-kernel@vger.kernel.org, 
	syzkaller-bugs@googlegroups.com
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, May 10, 2024 at 3:01=E2=80=AFAM Aleksandr Nogikh <nogikh@google.com=
> wrote:
> On Fri, May 10, 2024 at 1:27=E2=80=AFAM Paul Moore <paul@paul-moore.com> =
wrote:
> >
> > On Thu, May 9, 2024 at 4:14=E2=80=AFAM syzbot
> > <syzbot+8ffdaad8822cadf6ff4e@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    6d7ddd805123 Merge tag 'soc-fixes-6.9-3' of git://git=
kern..
> > > git tree:       upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=3D10c901b89=
80000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=3D758bb5b8f=
724c7ba
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=3D8ffdaad8822=
cadf6ff4e
> > > 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=3D17ed19b=
8980000
> >
> > 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.

--=20
paul-moore.com