syzbot


BUG: unable to handle kernel paging request in ft260_i2c_xfer

Status: upstream: reported on 2025/07/27 11:42
Reported-by: syzbot+8fdd2a82bb6d01852369@syzkaller.appspotmail.com
First crash: 11h44m, last: 11h44m

Sample crash report:
udc-core: couldn't find an available UDC or it's busy
misc raw-gadget: fail, usb_gadget_probe_driver returned -19
Unable to handle kernel paging request at virtual address dfff8000000000fd
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
[dfff8000000000fd] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4222 Comm: syz.2.20 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ft260_i2c_xfer+0xa8/0x58c drivers/hid/hid-ft260.c:561
lr : ft260_i2c_xfer+0x84/0x58c drivers/hid/hid-ft260.c:558
sp : ffff80001fbf79c0
x29: ffff80001fbf7a70 x28: dfff800000000000 x27: 0000000000000001
x26: 00000000000007e8 x25: ffff0000c950b200 x24: ffff0000d7c781ac
x23: dfff800000000000 x22: 1ffff00003f7ef40 x21: 00000000000000fd
x20: ffff80000ed1b390 x19: 0000000000000000 x18: 0000000000000000
x17: ffff800016d04000 x16: ffff8000082c0bc8 x15: ffff8000167e4500
x14: ffff0000c6a14080 x13: dfff800000000000 x12: 0000000000080000
x11: 00000000000026b8 x10: ffff8000241ca000 x9 : ffff80000ed1b414
x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800016ed8d90 x4 : 0000000000000000 x3 : 0000000000000010
x2 : 0000000000000001 x1 : ffff0000c950b200 x0 : ffff0000d7c78080
Call trace:
 ft260_i2c_xfer+0xa8/0x58c drivers/hid/hid-ft260.c:561
 __i2c_transfer+0x614/0x1fdc drivers/i2c/i2c-core-base.c:-1
 i2c_transfer+0x1c8/0x2e4 drivers/i2c/i2c-core-base.c:2330
 i2cdev_ioctl_rdwr+0x314/0x68c drivers/i2c/i2c-dev.c:297
 i2cdev_ioctl+0x7a8/0x9a4 drivers/i2c/i2c-dev.c:458
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:874 [inline]
 __se_sys_ioctl fs/ioctl.c:860 [inline]
 __arm64_sys_ioctl+0x14c/0x1c8 fs/ioctl.c:860
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 966c85ee f9400273 911fa27a d343ff55 (387c6aa8) 
---[ end trace a934b50eacbf2ca5 ]---
----------------
Code disassembly (best guess):
   0:	966c85ee 	bl	0xfffffffff9b217b8
   4:	f9400273 	ldr	x19, [x19]
   8:	911fa27a 	add	x26, x19, #0x7e8
   c:	d343ff55 	lsr	x21, x26, #3
* 10:	387c6aa8 	ldrb	w8, [x21, x28] <-- trapping instruction

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/27 11:41 linux-5.15.y c79648372d02 fb8f743d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in ft260_i2c_xfer
* Struck through repros no longer work on HEAD.