BUG: unable to handle kernel paging request in call_usermodehelper_exec_work

5 views
Skip to first unread message

syzbot

unread,
Nov 14, 2022, 7:29:43 PM11/14/22
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 1621b6eaebf7 Merge branch 'for-next/fixes' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=1202cb99880000
kernel config: https://syzkaller.appspot.com/x/.config?x=606e57fd25c5c6cc
dashboard link: https://syzkaller.appspot.com/bug?extid=9e69e91a8cb17766921b
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
CC: [bri...@redhat.com bse...@google.com dietmar....@arm.com juri....@redhat.com linux-...@vger.kernel.org mgo...@suse.de mi...@redhat.com pet...@infradead.org ros...@goodmis.org vincent...@linaro.org vsch...@redhat.com]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/82aa7741098d/disk-1621b6ea.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f6be08c4e4c2/vmlinux-1621b6ea.xz
kernel image: https://storage.googleapis.com/syzbot-assets/296b6946258a/Image-1621b6ea.gz.xz

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

Unable to handle kernel paging request at virtual address 0067c2d67a315ef8
Mem abort info:
ESR = 0x0000000096000004
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x04: level 0 translation fault
Data abort info:
ISV = 0, ISS = 0x00000004
CM = 0, WnR = 0
[0067c2d67a315ef8] address between user and kernel address ranges
Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 126 Comm: kworker/u4:3 Not tainted 6.1.0-rc4-syzkaller-31872-g1621b6eaebf7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Workqueue: events_unbound call_usermodehelper_exec_work
pstate: 004000c5 (nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : swake_up_locked kernel/sched/swait.c:29 [inline]
pc : complete+0x48/0x90 kernel/sched/completion.c:36
lr : complete+0x24/0x90 kernel/sched/completion.c:32
sp : ffff800012b73d20
x29: ffff800012b73d20 x28: ffff80000d24b000 x27: ffff0000c0028005
x26: ffff0000c2771010 x25: 0000000000000004 x24: ffff0000c0028005
x23: ffff00011cd4cc00 x22: ffff800013ab3ad8 x21: 6567c2d67a315f00
x20: 0000000000000000 x19: ffff800013ab3a98 x18: 0000000000000051
x17: ffff80000c04d83c x16: ffff80000db1a158 x15: ffff0000c23a0000
x14: 0000000000000040 x13: 00000000ffffffff x12: ffff0000c23a0000
x11: ff808000095f1718 x10: 0000000000000000 x9 : 0000000000000000
x8 : 000000000d30b989 x7 : ffff800008186f8c x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
swake_up_locked kernel/sched/swait.c:25 [inline]
complete+0x48/0x90 kernel/sched/completion.c:36
call_usermodehelper_exec_work+0x128/0x17c
process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
worker_thread+0x340/0x610 kernel/workqueue.c:2436
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863
Code: b90002c8 f8448ed5 eb1602bf 54000160 (f85f82a0)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: b90002c8 str w8, [x22]
4: f8448ed5 ldr x21, [x22, #72]!
8: eb1602bf cmp x21, x22
c: 54000160 b.eq 0x38 // b.none
* 10: f85f82a0 ldur x0, [x21, #-8] <-- trapping instruction


---
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 syzk...@googlegroups.com.

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

syzbot

unread,
Feb 8, 2023, 7:23:29 PM2/8/23
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages