From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f79.google.com (mail-oo1-f79.google.com [209.85.161.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 038803DA7D6 for ; Mon, 23 Mar 2026 20:13:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.79 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774296820; cv=none; b=cdT+BRbdZXl+knz75dduSzUsvpipPgv9Z++DAfKv5UZQUos/V41F4e55Xkek/H1P8nHvOuVN93qu1+uQYpV+umAPD8X2nF/k2i56UpVS+y6RGpl8N68UKeRJfzi3qxlkfylvF7fSj/p2hYx6cFSk7mDEcEzzLxx5laPmtBd4Lfo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774296820; c=relaxed/simple; bh=cj8ALMrx35H2DTMyqR4QEKUGwvRYO/9HFJ7GMEZ5JxY=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=lcj100Xli4DYZownhb9h1A7LlI5vBkGy2GrLteh3t0LxDQ05S32DcJaRdGeNB6ZhHGD01BmWcYoRPU4BqI98a1v/XQWZg0SnP9/DZY+1L9FaC4ZB45LZP9EversaYwG3WInx4ophRxnxc80//Vq6XvSJCwQE+99z+p+hgVQudv4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.161.79 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oo1-f79.google.com with SMTP id 006d021491bc7-67baeba7a53so70618369eaf.0 for ; Mon, 23 Mar 2026 13:13:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774296817; x=1774901617; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=0pEoFV3Z+GhDMvVnTuUQ5HLbi+15yPEKi/PRT6DkVAQ=; b=YI43Li5MoZlNCn435zZ8OsmI5FW1PzFn8DwJ3L0hIyBWLW1IphckMFtzvIH+I0UDrf jwTKq99M1Ag6RZd54NZAfgEGFpiaw+7L0p9qDB++7B/a9SB0VEeeh5izgA04iofkE2Zu iLVXwnp+8sY13uXEzeUu9mjlXzQY0nmcj7AjDYwia+0hpG95cKAmyto2jSestkI3D1xd GV/1oXAVNOfa/XIsW7iiwbxRmpv6rXOUyiXtiIn1dAV5wpMqO7zAE31ZbghXN3ja39w7 1/34fGM1OiSXg7HuwEVtR+sBaTbJ6TqvEyYPKQxdgcv51rqgY5r7NDJLHrHCnX9Iihix wirQ== X-Gm-Message-State: AOJu0YwXsmnq+Avx8bmwhl3wXgz5VwzgyZ5mfUkDAi6r5VTSVBFvPewZ u8PGZfUF0nVbTvrNEvTvqeQgeXdD8qgUPvsEThGjcerT0CM+FSfAS7aQ48/7eSDa+BH5TirT1vI Due4BSLlN8oba0Ela1IUhY0nzUG3vyiwciEm4HMLUvEHC6aaBJyahy676iDFk6g== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6820:3090:b0:67b:a4cb:293f with SMTP id 006d021491bc7-67df5d6a987mr683972eaf.17.1774296816960; Mon, 23 Mar 2026 13:13:36 -0700 (PDT) Date: Mon, 23 Mar 2026 13:13:36 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69c19ef0.050a0220.3bf4de.00aa.GAE@google.com> Subject: [syzbot] [media?] [usb?] KASAN: slab-out-of-bounds Read in ec168_i2c_xfer From: syzbot To: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-usb@vger.kernel.org, mchehab@kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 785f0eb2f85d Add linux-next specific files for 20260320 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=12cc5e02580000 kernel config: https://syzkaller.appspot.com/x/.config?x=c584910d0d74158d dashboard link: https://syzkaller.appspot.com/bug?extid=64485d3659c4c07111b4 compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1689e06a580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12e22cba580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/a1f7fd9c1a63/disk-785f0eb2.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/6c138da87c25/vmlinux-785f0eb2.xz kernel image: https://storage.googleapis.com/syzbot-assets/4d1be64e56db/bzImage-785f0eb2.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+64485d3659c4c07111b4@syzkaller.appspotmail.com ================================================================== BUG: KASAN: slab-out-of-bounds in ec168_i2c_xfer+0x4cd/0x640 drivers/media/usb/dvb-usb-v2/ec168.c:143 Read of size 1 at addr ffff888022a8e061 by task syz.0.17/6065 CPU: 0 UID: 0 PID: 6065 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_address_description+0x55/0x1e0 mm/kasan/report.c:378 print_report+0x58/0x70 mm/kasan/report.c:482 kasan_report+0x117/0x150 mm/kasan/report.c:595 ec168_i2c_xfer+0x4cd/0x640 drivers/media/usb/dvb-usb-v2/ec168.c:143 __i2c_transfer+0x79a/0x1f70 drivers/i2c/i2c-core-base.c:-1 i2c_transfer+0x1cc/0x2d0 drivers/i2c/i2c-core-base.c:2317 i2cdev_ioctl_rdwr+0x460/0x740 drivers/i2c/i2c-dev.c:306 i2cdev_ioctl+0x6a5/0x880 drivers/i2c/i2c-dev.c:467 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fc935d9c799 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffef6f8b6b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fc936015fa0 RCX: 00007fc935d9c799 RDX: 0000200000000140 RSI: 0000000000000707 RDI: 0000000000000004 RBP: 00007fc935e32c99 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fc936015fac R14: 00007fc936015fa0 R15: 00007fc936015fa0 Allocated by task 6065: kasan_save_stack mm/kasan/common.c:57 [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:78 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0x93/0xb0 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __do_kmalloc_node mm/slub.c:5292 [inline] __kmalloc_node_track_caller_noprof+0x4db/0x7b0 mm/slub.c:5400 memdup_user+0x2b/0xd0 mm/util.c:221 i2cdev_ioctl_rdwr+0x1c6/0x740 drivers/i2c/i2c-dev.c:266 i2cdev_ioctl+0x6a5/0x880 drivers/i2c/i2c-dev.c:467 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f The buggy address belongs to the object at ffff888022a8e060 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 [ffff888022a8e060, ffff888022a8e061) The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888022a8e260 pfn:0x22a8e flags: 0xfff00000000200(workingset|node=0|zone=1|lastcpupid=0x7ff) page_type: f5(slab) raw: 00fff00000000200 ffff88801b041500 ffffea0000a17150 ffffea0000cd6d90 raw: ffff888022a8e260 000000080080007b 00000000f5000000 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as allocated page last allocated via order 0, migratetype Unmovable, gfp_mask 0xd2cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 1, tgid 1 (swapper/0), ts 3746368734, free_ts 0 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x231/0x280 mm/page_alloc.c:1859 prep_new_page mm/page_alloc.c:1867 [inline] get_page_from_freelist+0x2418/0x24b0 mm/page_alloc.c:3926 __alloc_frozen_pages_noprof+0x233/0x3d0 mm/page_alloc.c:5213 alloc_slab_page mm/slub.c:3278 [inline] allocate_slab+0x77/0x660 mm/slub.c:3467 new_slab mm/slub.c:3525 [inline] refill_objects+0x339/0x3d0 mm/slub.c:7247 refill_sheaf mm/slub.c:2816 [inline] __pcs_replace_empty_main+0x321/0x720 mm/slub.c:4651 alloc_from_pcs mm/slub.c:4749 [inline] slab_alloc_node mm/slub.c:4883 [inline] __do_kmalloc_node mm/slub.c:5291 [inline] __kmalloc_noprof+0x474/0x760 mm/slub.c:5304 kmalloc_noprof include/linux/slab.h:954 [inline] kzalloc_noprof include/linux/slab.h:1188 [inline] acpi_ns_internalize_name+0x2c9/0x3e0 drivers/acpi/acpica/nsutils.c:331 acpi_ns_get_node_unlocked+0x186/0x480 drivers/acpi/acpica/nsutils.c:666 acpi_ns_get_node+0x76/0xc0 drivers/acpi/acpica/nsutils.c:726 acpi_ns_evaluate+0x283/0x1230 drivers/acpi/acpica/nseval.c:62 acpi_evaluate_object+0x657/0xd50 drivers/acpi/acpica/nsxfeval.c:354 acpi_evaluate_dsm drivers/acpi/utils.c:797 [inline] acpi_check_dsm+0x1bb/0x6f0 drivers/acpi/utils.c:830 device_has_acpi_name drivers/pci/pci-label.c:44 [inline] acpi_attr_is_visible+0x89/0xe0 drivers/pci/pci-label.c:221 create_files fs/sysfs/group.c:69 [inline] internal_create_group+0x5e5/0x1180 fs/sysfs/group.c:189 internal_create_groups fs/sysfs/group.c:229 [inline] sysfs_create_groups+0x59/0x120 fs/sysfs/group.c:255 page_owner free stack trace missing Memory state around the buggy address: ffff888022a8df00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff888022a8df80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff888022a8e000: fa fc fc fc fa fc fc fc fa fc fc fc 01 fc fc fc ^ ffff888022a8e080: 00 fc fc fc fa fc fc fc fa fc fc fc 07 fc fc fc ffff888022a8e100: 07 fc fc fc 05 fc fc fc fa fc fc fc 06 fc fc fc ================================================================== --- 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@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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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