[v5.15] BUG: unable to handle kernel paging request in device_move

0 views
Skip to first unread message

syzbot

unread,
Dec 16, 2024, 6:50:26 AMDec 16
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 963e654022cc Linux 5.15.174
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14ca34f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=be5e2d52ec7084cf
dashboard link: https://syzkaller.appspot.com/bug?extid=6face46c1d2f28e76643
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c39b959d0e47/disk-963e6540.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1b11b7541d5f/vmlinux-963e6540.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0969216fb32b/Image-963e6540.gz.xz

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

Unable to handle kernel paging request at virtual address dfff80000000000b
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff80000000000b] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5385 Comm: syz.3.435 Not tainted 5.15.174-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : klist_put lib/klist.c:212 [inline]
pc : klist_del lib/klist.c:230 [inline]
pc : klist_remove+0x190/0x38c lib/klist.c:249
lr : spin_unlock include/linux/spinlock.h:403 [inline]
lr : klist_remove+0x16c/0x38c lib/klist.c:247
sp : ffff8000201b7400
x29: ffff8000201b74a0 x28: dfff800000000000 x27: 1fffe0001ba368c9
x26: ffff0000d160b680 x25: dfff800000000000 x24: ffff700004036e80
x23: ffff800015351628 x22: 1fffe0001ccf908c x21: 0000000000000000
x20: ffff8000201b7420 x19: ffff0000e67c8460 x18: ffff8000201b70e0
x17: 0000000000000000 x16: ffff80000824ec04 x15: 0000000000035b15
x14: 000000001be97231 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000001 x10: 0000000000000000 x9 : 1fffe0001a2c16d1
x8 : 000000000000000b x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800017a67370 x4 : 0000000000000008 x3 : ffff800008305a08
x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000058
Call trace:
klist_put lib/klist.c:212 [inline]
klist_del lib/klist.c:230 [inline]
klist_remove+0x190/0x38c lib/klist.c:249
device_move+0x17c/0x5c8 drivers/base/core.c:4338
hci_conn_del_sysfs+0xa0/0x154 net/bluetooth/hci_sysfs.c:73
hci_conn_cleanup+0x424/0x5b8 net/bluetooth/hci_conn.c:140
hci_conn_del+0x238/0x378 net/bluetooth/hci_conn.c:678
hci_conn_hash_flush+0x188/0x220 net/bluetooth/hci_conn.c:1623
hci_dev_do_close+0x7e4/0x1060 net/bluetooth/hci_core.c:1795
hci_unregister_dev+0x248/0x4d4 net/bluetooth/hci_core.c:4040
vhci_release+0x74/0xc4 drivers/bluetooth/hci_vhci.c:345
__fput+0x1c4/0x800 fs/file_table.c:280
____fput+0x20/0x30 fs/file_table.c:308
task_work_run+0x130/0x1e4 kernel/task_work.c:188
exit_task_work include/linux/task_work.h:33 [inline]
do_exit+0x670/0x20bc kernel/exit.c:874
do_group_exit+0x110/0x268 kernel/exit.c:996
get_signal+0x634/0x1550 kernel/signal.c:2900
do_signal arch/arm64/kernel/signal.c:890 [inline]
do_notify_resume+0x3d0/0x32b8 arch/arm64/kernel/signal.c:943
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_svc+0xfc/0x1f0 arch/arm64/kernel/entry-common.c:609
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: f9400268 927ff915 910162a0 d343fc08 (38796908)
---[ end trace 354f62933b96c1d1 ]---
----------------
Code disassembly (best guess):
0: f9400268 ldr x8, [x19]
4: 927ff915 and x21, x8, #0xfffffffffffffffe
8: 910162a0 add x0, x21, #0x58
c: d343fc08 lsr x8, x0, #3
* 10: 38796908 ldrb w8, [x8, x25] <-- 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.

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

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

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

If you want to undo deduplication, reply with:
#syz undup
Reply all
Reply to author
Forward
0 new messages