linux-kernel - [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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <000000000000da2a8505fb71d81b@google.com>
Date:   Thu, 11 May 2023 14:41:11 -0700
From:   syzbot <syzbot+afc1d968649e7e851562@...kaller.appspotmail.com>
To:     geert+renesas@...der.be, 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
Subject: [syzbot] upstream boot error: BUG: unable to handle kernel NULL
 pointer dereference in gic_eoi_irq

Hello,

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
LR is at handle_percpu_devid_irq+0xb8/0x2d4 kernel/irq/chip.c:944
pc : [<8087e328>]    lr : [<802bf798>]    psr: 20000193
sp : df805f60  ip : df805f78  fp : df805f74
r10: 00000000  r9 : 831f4680  r8 : 00000001
r7 : 0000001c  r6 : 81b0febc  r5 : 000005f0  r4 : 8309a218
r3 : 000005f0  r2 : 0009127a  r1 : ddde8b00  r0 : 8309a218
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment none
Control: 30c5387d  Table: 84804d80  DAC: 00000000
Register r0 information: slab kmalloc-256 start 8309a200 pointer offset 24 size 256
Register r1 information: non-slab/vmalloc memory
Register r2 information:
8<--- cut here ---
Unable to handle kernel NULL pointer dereference at virtual address 000001ff when read
[000001ff] *pgd=80000080004003, *pmd=00000000
Internal error: Oops: 207 [#2] 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 __find_vmap_area mm/vmalloc.c:841 [inline]
PC is at find_vmap_area mm/vmalloc.c:1862 [inline]
PC is at find_vm_area mm/vmalloc.c:2623 [inline]
PC is at vmalloc_dump_obj+0x38/0xb4 mm/vmalloc.c:4221
LR is at __raw_spin_lock include/linux/spinlock_api_smp.h:132 [inline]
LR is at _raw_spin_lock+0x18/0x58 kernel/locking/spinlock.c:154
pc : [<8047a2ec>]    lr : [<81801fd4>]    psr: 20000193
sp : df805df0  ip : df805dd8  fp : df805e04
r10: 831f4680  r9 : 8261c9a4  r8 : 8285041c
r7 : 60000193  r6 : 00000003  r5 : 00092000  r4 : 00000207
r3 : 830e13a0  r2 : 00001dda  r1 : 00000000  r0 : 00000001
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment none
Control: 30c5387d  Table: 84804d80  DAC: 00000000


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup