linux-kernel - Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in gic_eoi

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMuHMdUzcWjyx8xmjQwJh7r27RS-2p__X1cUFUWJVKmJM=AgeQ@mail.gmail.com>
Date:   Fri, 12 May 2023 13:57:35 +0200
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Aleksandr Nogikh <nogikh@...gle.com>
Cc:     syzbot <syzbot+afc1d968649e7e851562@...kaller.appspotmail.com>,
        linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
        magnus.damm@...il.com, maz@...nel.org,
        syzkaller-bugs@...glegroups.com, tglx@...utronix.de,
        syzkaller@...glegroups.com
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL
 pointer dereference in gic_eoi_irq

Hi Aleksandr,

On Fri, May 12, 2023 at 1:30 PM Aleksandr Nogikh <nogikh@...gle.com> wrote:
> On Fri, May 12, 2023 at 9:59 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > On Thu, May 11, 2023 at 11:41 PM syzbot
> > <syzbot+afc1d968649e7e851562@...kaller.appspotmail.com> wrote:
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    ac9a78681b92 Linux 6.4-rc1
> > > git tree:       upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=102a3f6a280000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=cc86fee67199911d
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=afc1d968649e7e851562
> > > compiler:       arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> > > userspace arch: arm
> > >
> > > Downloadable assets:
> > > disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/c35b5b2731d2/non_bootable_disk-ac9a7868.raw.xz
> > > vmlinux: https://storage.googleapis.com/syzbot-assets/c04bec59d77d/vmlinux-ac9a7868.xz
> > > kernel image: https://storage.googleapis.com/syzbot-assets/070113b307f3/zImage-ac9a7868.xz
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+afc1d968649e7e851562@...kaller.appspotmail.com
> > >
> > > 8<--- cut here ---
> > > Unable to handle kernel NULL pointer dereference at virtual address 000005f4 when read
> > > [000005f4] *pgd=80000080004003, *pmd=00000000
> > > Internal error: Oops: 207 [#1] PREEMPT SMP ARM
> > > Modules linked in:
> > > CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.4.0-rc1-syzkaller #0
> > > Hardware name: ARM-Versatile Express
> > > PC is at gic_eoi_irq+0x64/0x70 drivers/irqchip/irq-gic.c:228
> >
> > Why is this sent to the renesas-soc maintainers?
>
> The report was attributed to `drivers/irqchip/irq-gic.c` and
> `./scripts/get_maintainer.pl -f drivers/irqchip/irq-gic.c` gives
> linux-renesas-soc@...r.kernel.org (open list:ARM/RISC-V/RENESAS ARCHITECTURE)
> as one of the output results.

Oh, right, there's a small quirk for renesas,emev in the GIC driver.

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds