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

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]

Date:   Tue, 02 May 2023 12:13:47 -0700
From:   syzbot <syzbot+9ccf090539dced888489@...kaller.appspotmail.com>
To:     linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
        tglx@...utronix.de
Subject: [syzbot] upstream boot error: BUG: unable to handle kernel NULL
 pointer dereference in generic_handle_domain_irq

Hello,

syzbot found the following issue on:

HEAD commit:    d7b3ffe2d7e4 Merge tag 'backlight-next-6.4' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a288c4280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=124f13edd5df0b0d
dashboard link: https://syzkaller.appspot.com/bug?extid=9ccf090539dced888489
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

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9ccf090539dced888489@...kaller.appspotmail.com

8<--- cut here ---
Unable to handle kernel NULL pointer dereference at virtual address 0000003b when read
[0000003b] *pgd=80000080004003, *pmd=00000000
Internal error: Oops: 207 [#1] PREEMPT SMP ARM
Modules linked in:
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-syzkaller #0
Hardware name: ARM-Versatile Express
PC is at generic_handle_irq_desc include/linux/irqdesc.h:158 [inline]
PC is at handle_irq_desc kernel/irq/irqdesc.c:651 [inline]
PC is at generic_handle_domain_irq+0x20/0x40 kernel/irq/irqdesc.c:707
LR is at rcu_read_unlock include/linux/rcupdate.h:805 [inline]
LR is at __irq_resolve_mapping+0x54/0x90 kernel/irq/irqdomain.c:973
pc : [<802b8fb8>]    lr : [<802c0e00>]    psr: a0000193
sp : 82601e78  ip : 82601e58  fp : 82601e84
r10: 00000000  r9 : 8261ae40  r8 : 00000000
r7 : df80a00c  r6 : 824aebe0  r5 : df80a000  r4 : 8260cdf4
r3 : ffffffff  r2 : 8261ae40  r1 : 0000001b  r0 : ffffffff
Flags: NzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 30c5387d  Table: 84a1e300  DAC: fffffffd
Register r0 information: non-paged memory
Register r1 information: non-paged memory
Register r2 information: non-slab/vmalloc memory
Register r3 information: non-paged memory
Register r4 information: non-slab/vmalloc memory
Register r5 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: 0 PID: 0 Comm: swapper/0 Not tainted 6.3.0-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 : [<8047a1f0>]    lr : [<8180165c>]    psr: 20000193
sp : 82601d08  ip : 82601cf0  fp : 82601d1c
r10: 8261ae40  r9 : 8261c9a4  r8 : 8285041c
r7 : 60000193  r6 : 00000006  r5 : df80a000  r4 : 00000207
r3 : 80216638  r2 : 00002003  r1 : 00000000  r0 : 00000001
Flags: nzCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 30c5387d  Table: 84a1e300  DAC: fffffffd


---
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