==================================================================
BUG: KASAN: slab-out-of-bounds in ec168_i2c_xfer+0x3a0/0x500 drivers/media/usb/dvb-usb-v2/ec168.c:143
Read of size 1 at addr ffff0000c2e46301 by task syz.0.17/4933

CPU: 1 UID: 0 PID: 4933 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/23/2026
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 print_address_description+0xb0/0x238 mm/kasan/report.c:378
 print_report+0x68/0x84 mm/kasan/report.c:482
 kasan_report+0x8c/0xc4 mm/kasan/report.c:595
 __asan_report_load1_noabort+0x20/0x2c mm/kasan/report_generic.c:378
 ec168_i2c_xfer+0x3a0/0x500 drivers/media/usb/dvb-usb-v2/ec168.c:143
 __i2c_transfer+0x610/0x1794 drivers/i2c/i2c-core-base.c:-1
 i2c_transfer+0x1cc/0x2e0 drivers/i2c/i2c-core-base.c:2350
 i2cdev_ioctl_rdwr+0x36c/0x6c4 drivers/i2c/i2c-dev.c:306
 i2cdev_ioctl+0x608/0x7e0 drivers/i2c/i2c-dev.c:467
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __arm64_sys_ioctl+0x154/0x1cc fs/ioctl.c:583
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796
 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606

Allocated by task 4933:
 kasan_save_stack mm/kasan/common.c:57 [inline]
 kasan_save_track+0x40/0x78 mm/kasan/common.c:78
 kasan_save_alloc_info+0x40/0x50 mm/kasan/generic.c:570
 poison_kmalloc_redzone mm/kasan/common.c:409 [inline]
 __kasan_kmalloc+0x9c/0xb4 mm/kasan/common.c:426
 kasan_kmalloc include/linux/kasan.h:263 [inline]
 __do_kmalloc_node mm/slub.c:5414 [inline]
 __kmalloc_node_track_caller_noprof+0x440/0x6e0 mm/slub.c:5545
 memdup_user+0x44/0xec mm/util.c:221
 i2cdev_ioctl_rdwr+0x17c/0x6c4 drivers/i2c/i2c-dev.c:266
 i2cdev_ioctl+0x608/0x7e0 drivers/i2c/i2c-dev.c:467
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:597 [inline]
 __se_sys_ioctl fs/ioctl.c:583 [inline]
 __arm64_sys_ioctl+0x154/0x1cc fs/ioctl.c:583
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x244 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0xec/0x23c arch/arm64/kernel/syscall.c:121
 do_el0_svc+0x4c/0x5c arch/arm64/kernel/syscall.c:140
 el0_svc+0x60/0x1d8 arch/arm64/kernel/entry-common.c:796
 el0t_64_sync_handler+0x44/0x104 arch/arm64/kernel/entry-common.c:815
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:606

The buggy address belongs to the object at ffff0000c2e46300
 which belongs to the cache kmalloc-8 of size 8
The buggy address is located 0 bytes to the right of
 allocated 1-byte region [ffff0000c2e46300, ffff0000c2e46301)

The buggy address belongs to the physical page:
page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff0000c2e46e80 pfn:0x102e46
flags: 0x5ffc00000000200(workingset|node=0|zone=2|lastcpupid=0x7ff)
page_type: f5(slab)
raw: 05ffc00000000200 ffff0000c0001500 fffffdffc357b350 fffffdffc357a450
raw: ffff0000c2e46e80 000000000080007d 00000000f5000000 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000c2e46200: 00 fc fc fc 00 fc fc fc 00 fc fc fc 00 fc fc fc
 ffff0000c2e46280: 00 fc fc fc 00 fc fc fc 00 fc fc fc 00 fc fc fc
>ffff0000c2e46300: 01 fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc
                   ^
 ffff0000c2e46380: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc
 ffff0000c2e46400: fa fc fc fc fa fc fc fc fa fc fc fc fa fc fc fc
==================================================================