[v5.15] KASAN: stack-out-of-bounds Read in cp2112_xfer
6 views
Skip to first unread message
syzbot
Nov 12, 2025, 8:43:30 PMNov 12
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ed4914580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=9c7c53be91054ae17acf
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9c7c53...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
Read of size 42 at addr ffffc9000338fd41 by task syz.6.313/5563
CPU: 1 PID: 5563 Comm: syz.6.313 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
print_address_description+0x60/0x2d0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0xdf/0x130 mm/kasan/report.c:451
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x733/0x1d50 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff7678c66c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff765b2d038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff767b1cfa0 RCX: 00007ff7678c66c9
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007ff767948f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff767b1d038 R14: 00007ff767b1cfa0 R15: 00007ffd30726098
</TASK>
addr ffffc9000338fd41 is located in stack of task syz.6.313/5563 at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x650
this frame has 1 object:
[32, 66) 'temp'
Memory state around the buggy address:
ffffc9000338fc00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
ffffc9000338fc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000338fd00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc9000338fd80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc9000338fe00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
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
syzbot found the following issue on:
HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ed4914580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=9c7c53be91054ae17acf
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9c7c53...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
Read of size 42 at addr ffffc9000338fd41 by task syz.6.313/5563
CPU: 1 PID: 5563 Comm: syz.6.313 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
print_address_description+0x60/0x2d0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0xdf/0x130 mm/kasan/report.c:451
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x733/0x1d50 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7ff7678c66c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ff765b2d038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007ff767b1cfa0 RCX: 00007ff7678c66c9
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007ff767948f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff767b1d038 R14: 00007ff767b1cfa0 R15: 00007ffd30726098
</TASK>
addr ffffc9000338fd41 is located in stack of task syz.6.313/5563 at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x650
this frame has 1 object:
[32, 66) 'temp'
Memory state around the buggy address:
ffffc9000338fc00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
ffffc9000338fc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000338fd00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc9000338fd80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc9000338fe00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
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
syzbot
Nov 12, 2025, 9:45:32 PMNov 12
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: f6e38ae624cf Linux 6.1.158
syzbot found the following issue on:
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=101a360a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=78f74668e7b6e051c055
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2b7003e2661d/disk-f6e38ae6.raw.xz
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
vmlinux: https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:482 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x60b/0xdd0 drivers/hid/hid-cp2112.c:699
Read of size 42 at addr ffffc90003497d41 by task syz.3.2161/12303
CPU: 1 PID: 12303 Comm: syz.3.2161 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
Call Trace:
<TASK>
print_address_description mm/kasan/report.c:316 [inline]
print_report+0xa8/0x210 mm/kasan/report.c:420
kasan_report+0x10b/0x140 mm/kasan/report.c:524
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:482 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_xfer+0x60b/0xdd0 drivers/hid/hid-cp2112.c:699
__i2c_smbus_xfer+0x771/0x1fc0 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fc84098f6c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc83ebf6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fc840be5fa0 RCX: 00007fc84098f6c9
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007fc840a11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fc840be6038 R14: 00007fc840be5fa0 R15: 00007ffce1abb248
</TASK>
The buggy address belongs to stack of task syz.3.2161/12303
and is located at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x650
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to a 8-page vmalloc region starting at 0xffffc90003490000 allocated at copy_process+0x5bd/0x4020 kernel/fork.c:2181
The buggy address belongs to the physical page:
page:ffffea0000809640 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x20259
memcg:ffff88803091fd02
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88803091fd02
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 3638, tgid 3638 (udevd), ts 900532831572, free_ts 896650305034
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2532
prep_new_page mm/page_alloc.c:2539 [inline]
get_page_from_freelist+0x1a26/0x1ac0 mm/page_alloc.c:4328
__alloc_pages+0x1df/0x4e0 mm/page_alloc.c:5614
vm_area_alloc_pages mm/vmalloc.c:3002 [inline]
__vmalloc_area_node mm/vmalloc.c:3071 [inline]
__vmalloc_node_range+0x959/0x1390 mm/vmalloc.c:3243
alloc_thread_stack_node kernel/fork.c:312 [inline]
dup_task_struct+0x3d3/0x6b0 kernel/fork.c:989
copy_process+0x5bd/0x4020 kernel/fork.c:2181
kernel_clone+0x225/0x8b0 kernel/fork.c:2757
__do_sys_clone kernel/fork.c:2898 [inline]
__se_sys_clone kernel/fork.c:2882 [inline]
__x64_sys_clone+0x17c/0x1d0 kernel/fork.c:2882
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1459 [inline]
free_pcp_prepare mm/page_alloc.c:1509 [inline]
free_unref_page_prepare+0x8b4/0x9a0 mm/page_alloc.c:3384
free_unref_page+0x2e/0x3f0 mm/page_alloc.c:3479
__vunmap+0x856/0xa00 mm/vmalloc.c:2726
do_free_pages sound/core/pcm_memory.c:93 [inline]
snd_pcm_lib_free_pages+0x1e4/0x2a0 sound/core/pcm_memory.c:499
do_hw_free sound/core/pcm_native.c:888 [inline]
snd_pcm_release_substream+0x29e/0x460 sound/core/pcm_native.c:2721
snd_pcm_oss_release_file sound/core/oss/pcm_oss.c:2412 [inline]
snd_pcm_oss_release+0x143/0x240 sound/core/oss/pcm_oss.c:2591
__fput+0x22c/0x920 fs/file_table.c:320
task_work_run+0x1ca/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Memory state around the buggy address:
ffffc90003497c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90003497d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc90003497d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90003497e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
syzbot
Nov 13, 2025, 12:47:31 AMNov 13
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17212884580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10013532580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9c7c53...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
Read of size 42 at addr ffffc900030dfd41 by task syz.0.17/4318
CPU: 0 PID: 4318 Comm: syz.0.17 Not tainted syzkaller #0
RAX: ffffffffffffffda RBX: 00007f30fd2a0fa0 RCX: 00007f30fd04a6c9
</TASK>
addr ffffc900030dfd41 is located in stack of task syz.0.17/4318 at offset 33 in frame:
ffffc900030dfc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc900030dfd00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc900030dfd80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc900030dfe00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
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.
HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
kernel config: https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link: https://syzkaller.appspot.com/bug?extid=9c7c53be91054ae17acf
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1115897c580000
dashboard link: https://syzkaller.appspot.com/bug?extid=9c7c53be91054ae17acf
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10013532580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9c7c53...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
CPU: 0 PID: 4318 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
print_address_description+0x60/0x2d0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0xdf/0x130 mm/kasan/report.c:451
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x733/0x1d50 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f30fd04a6c9
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
print_address_description+0x60/0x2d0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0xdf/0x130 mm/kasan/report.c:451
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:481 [inline]
cp2112_xfer+0x87c/0xe00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x733/0x1d50 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffff7cbcc68 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f30fd2a0fa0 RCX: 00007f30fd04a6c9
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007f30fd0ccf91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f30fd2a0fa0 R14: 00007f30fd2a0fa0 R15: 0000000000000003
</TASK>
addr ffffc900030dfd41 is located in stack of task syz.0.17/4318 at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x650
this frame has 1 object:
[32, 66) 'temp'
Memory state around the buggy address:
ffffc900030dfc00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
this frame has 1 object:
[32, 66) 'temp'
Memory state around the buggy address:
ffffc900030dfc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc900030dfd00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc900030dfd80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc900030dfe00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
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.
syzbot
Nov 13, 2025, 1:51:28 AMNov 13
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151af0b4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=143cc658580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2b7003e2661d/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+78f746...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:482 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x60b/0xdd0 drivers/hid/hid-cp2112.c:699
Read of size 42 at addr ffffc90004097d41 by task syz.0.17/4436
CPU: 0 PID: 4436 Comm: syz.0.17 Not tainted syzkaller #0
RAX: ffffffffffffffda RBX: 00007f602ebe5fa0 RCX: 00007f602e98f6c9
</TASK>
The buggy address belongs to stack of task syz.0.17/4436
memcg:ffff88802fe54f82
create_kthread kernel/kthread.c:399 [inline]
kthreadd+0x536/0x6e0 kernel/kthread.c:748
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
release_pages+0x1f92/0x2200 mm/swap.c:1035
tlb_batch_pages_flush mm/mmu_gather.c:59 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:254 [inline]
tlb_flush_mmu+0xff/0x210 mm/mmu_gather.c:261
tlb_finish_mmu+0xbd/0x1c0 mm/mmu_gather.c:361
exit_mmap+0x343/0x8e0 mm/mmap.c:3262
__mmput+0x118/0x3c0 kernel/fork.c:1200
exit_mm+0x1e6/0x2c0 kernel/exit.c:565
do_exit+0x8c1/0x2400 kernel/exit.c:867
do_group_exit+0x217/0x2d0 kernel/exit.c:1022
__do_sys_exit_group kernel/exit.c:1033 [inline]
__se_sys_exit_group kernel/exit.c:1031 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1031
ffffc90004097c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90004097d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc90004097d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90004097e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
HEAD commit: f6e38ae624cf Linux 6.1.158
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=78f74668e7b6e051c055
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132f4914580000
dashboard link: https://syzkaller.appspot.com/bug?extid=78f74668e7b6e051c055
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=143cc658580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2b7003e2661d/disk-f6e38ae6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0696cea8d016/vmlinux-f6e38ae6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6b7a89e636d7/bzImage-f6e38ae6.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+78f746...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:482 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x60b/0xdd0 drivers/hid/hid-cp2112.c:699
CPU: 0 PID: 4436 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
print_address_description mm/kasan/report.c:316 [inline]
print_report+0xa8/0x210 mm/kasan/report.c:420
kasan_report+0x10b/0x140 mm/kasan/report.c:524
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:482 [inline]
cp2112_xfer+0x60b/0xdd0 drivers/hid/hid-cp2112.c:699
__i2c_smbus_xfer+0x771/0x1fc0 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f602e98f6c9
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
print_address_description mm/kasan/report.c:316 [inline]
print_report+0xa8/0x210 mm/kasan/report.c:420
kasan_report+0x10b/0x140 mm/kasan/report.c:524
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x27b/0x290 mm/kasan/generic.c:189
memcpy+0x25/0x60 mm/kasan/shadow.c:65
cp2112_write_req drivers/hid/hid-cp2112.c:482 [inline]
cp2112_xfer+0x60b/0xdd0 drivers/hid/hid-cp2112.c:699
__i2c_smbus_xfer+0x771/0x1fc0 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x263/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x3e3/0x650 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x545/0x750 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffefb4d9468 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f602ebe5fa0 RCX: 00007f602e98f6c9
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007f602ea11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f602ebe5fa0 R14: 00007f602ebe5fa0 R15: 0000000000000003
</TASK>
The buggy address belongs to stack of task syz.0.17/4436
and is located at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x650
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to a 8-page vmalloc region starting at 0xffffc90004090000 allocated at copy_process+0x5bd/0x4020 kernel/fork.c:2181
i2cdev_ioctl_smbus+0x0/0x650
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to the physical page:
page:ffffea0001efa640 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7be99
memcg:ffff88802fe54f82
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88802fe54f82
raw: 00fff00000000000 0000000000000000 dead000000000122 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 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 2, tgid 2 (kthreadd), ts 80965016314, free_ts 66080083383
page_owner tracks the page as allocated
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2532
prep_new_page mm/page_alloc.c:2539 [inline]
get_page_from_freelist+0x1a26/0x1ac0 mm/page_alloc.c:4328
__alloc_pages+0x1df/0x4e0 mm/page_alloc.c:5614
vm_area_alloc_pages mm/vmalloc.c:3002 [inline]
__vmalloc_area_node mm/vmalloc.c:3071 [inline]
__vmalloc_node_range+0x959/0x1390 mm/vmalloc.c:3243
alloc_thread_stack_node kernel/fork.c:312 [inline]
dup_task_struct+0x3d3/0x6b0 kernel/fork.c:989
copy_process+0x5bd/0x4020 kernel/fork.c:2181
kernel_clone+0x225/0x8b0 kernel/fork.c:2757
kernel_thread+0xe5/0x140 kernel/fork.c:2817
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2532
prep_new_page mm/page_alloc.c:2539 [inline]
get_page_from_freelist+0x1a26/0x1ac0 mm/page_alloc.c:4328
__alloc_pages+0x1df/0x4e0 mm/page_alloc.c:5614
vm_area_alloc_pages mm/vmalloc.c:3002 [inline]
__vmalloc_area_node mm/vmalloc.c:3071 [inline]
__vmalloc_node_range+0x959/0x1390 mm/vmalloc.c:3243
alloc_thread_stack_node kernel/fork.c:312 [inline]
dup_task_struct+0x3d3/0x6b0 kernel/fork.c:989
copy_process+0x5bd/0x4020 kernel/fork.c:2181
kernel_clone+0x225/0x8b0 kernel/fork.c:2757
create_kthread kernel/kthread.c:399 [inline]
kthreadd+0x536/0x6e0 kernel/kthread.c:748
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1459 [inline]
free_pcp_prepare mm/page_alloc.c:1509 [inline]
free_unref_page_prepare+0x8b4/0x9a0 mm/page_alloc.c:3384
free_unref_page_list+0xbb/0x8e0 mm/page_alloc.c:3525
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1459 [inline]
free_pcp_prepare mm/page_alloc.c:1509 [inline]
free_unref_page_prepare+0x8b4/0x9a0 mm/page_alloc.c:3384
release_pages+0x1f92/0x2200 mm/swap.c:1035
tlb_batch_pages_flush mm/mmu_gather.c:59 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:254 [inline]
tlb_flush_mmu+0xff/0x210 mm/mmu_gather.c:261
tlb_finish_mmu+0xbd/0x1c0 mm/mmu_gather.c:361
exit_mmap+0x343/0x8e0 mm/mmap.c:3262
__mmput+0x118/0x3c0 kernel/fork.c:1200
exit_mm+0x1e6/0x2c0 kernel/exit.c:565
do_exit+0x8c1/0x2400 kernel/exit.c:867
do_group_exit+0x217/0x2d0 kernel/exit.c:1022
__do_sys_exit_group kernel/exit.c:1033 [inline]
__se_sys_exit_group kernel/exit.c:1031 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1031
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Memory state around the buggy address:
ffffc90004097c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
ffffc90004097c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90004097d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc90004097d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90004097e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
syzbot
Nov 19, 2025, 12:27:26 AMNov 19
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ac9658580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=efbf3074a9bd9a22b326
disk image: https://storage.googleapis.com/syzbot-assets/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+efbf30...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
Read of size 42 at addr ffffc9000ba47d41 by task syz.0.8746/27249
CPU: 0 PID: 27249 Comm: syz.0.8746 Not tainted syzkaller #0
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x220 mm/kasan/report.c:468
kasan_report+0x117/0x150 mm/kasan/report.c:581
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x288/0x290 mm/kasan/generic.c:187
__asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x888/0x1d90 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x267/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x423/0x670 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x5d1/0x7e0 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7be218f6c9
RAX: ffffffffffffffda RBX: 00007f7be23e5fa0 RCX: 00007f7be218f6c9
</TASK>
The buggy address belongs to stack of task syz.0.8746/27249
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to a 8-page vmalloc region starting at 0xffffc9000ba40000 allocated at copy_process+0x549/0x3d70 kernel/fork.c:2331
memcg:ffff88802e8a6502
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
vm_area_alloc_pages mm/vmalloc.c:3089 [inline]
__vmalloc_area_node mm/vmalloc.c:3158 [inline]
__vmalloc_node_range+0x96b/0x1320 mm/vmalloc.c:3339
alloc_thread_stack_node kernel/fork.c:310 [inline]
dup_task_struct+0x3d0/0x7c0 kernel/fork.c:1124
copy_process+0x549/0x3d70 kernel/fork.c:2331
kernel_clone+0x21b/0x840 kernel/fork.c:2914
__do_sys_clone3 kernel/fork.c:3215 [inline]
__se_sys_clone3+0x252/0x2c0 kernel/fork.c:3199
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2475
release_pages+0x1fa0/0x2220 mm/swap.c:1022
tlb_batch_pages_flush mm/mmu_gather.c:98 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:293 [inline]
tlb_flush_mmu+0x368/0x4f0 mm/mmu_gather.c:300
tlb_finish_mmu+0xc3/0x1d0 mm/mmu_gather.c:392
exit_mmap+0x3f0/0xb50 mm/mmap.c:3315
__mmput+0x118/0x3c0 kernel/fork.c:1355
exit_mm+0x1da/0x2c0 kernel/exit.c:569
do_exit+0x88e/0x23c0 kernel/exit.c:870
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
Memory state around the buggy address:
ffffc9000ba47c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
ffffc9000ba47c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000ba47d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc9000ba47d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc9000ba47e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
syzbot found the following issue on:
HEAD commit: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12ac9658580000
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=efbf3074a9bd9a22b326
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
Read of size 42 at addr ffffc9000ba47d41 by task syz.0.8746/27249
CPU: 0 PID: 27249 Comm: syz.0.8746 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
Call Trace:
<TASK>
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x220 mm/kasan/report.c:468
kasan_report+0x117/0x150 mm/kasan/report.c:581
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x288/0x290 mm/kasan/generic.c:187
__asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x888/0x1d90 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x267/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x423/0x670 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x5d1/0x7e0 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7be218f6c9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7be300f038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f7be23e5fa0 RCX: 00007f7be218f6c9
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007f7be2211f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7be23e6038 R14: 00007f7be23e5fa0 R15: 00007ffde03fd7c8
</TASK>
The buggy address belongs to stack of task syz.0.8746/27249
and is located at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x670
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to the physical page:
page:ffffea000188f7c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x623df
memcg:ffff88802e8a6502
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88802e8a6502
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 27153, tgid 27153 (syz.0.8703), ts 1502369946820, free_ts 1478239683310
page_owner tracks the page as allocated
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
vm_area_alloc_pages mm/vmalloc.c:3089 [inline]
__vmalloc_area_node mm/vmalloc.c:3158 [inline]
__vmalloc_node_range+0x96b/0x1320 mm/vmalloc.c:3339
alloc_thread_stack_node kernel/fork.c:310 [inline]
dup_task_struct+0x3d0/0x7c0 kernel/fork.c:1124
copy_process+0x549/0x3d70 kernel/fork.c:2331
kernel_clone+0x21b/0x840 kernel/fork.c:2914
__do_sys_clone3 kernel/fork.c:3215 [inline]
__se_sys_clone3+0x252/0x2c0 kernel/fork.c:3199
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
reset_page_owner include/linux/page_owner.h:24 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page_list+0xbe/0x860 mm/page_alloc.c:2475
release_pages+0x1fa0/0x2220 mm/swap.c:1022
tlb_batch_pages_flush mm/mmu_gather.c:98 [inline]
tlb_flush_mmu_free mm/mmu_gather.c:293 [inline]
tlb_flush_mmu+0x368/0x4f0 mm/mmu_gather.c:300
tlb_finish_mmu+0xc3/0x1d0 mm/mmu_gather.c:392
exit_mmap+0x3f0/0xb50 mm/mmap.c:3315
__mmput+0x118/0x3c0 kernel/fork.c:1355
exit_mm+0x1da/0x2c0 kernel/exit.c:569
do_exit+0x88e/0x23c0 kernel/exit.c:870
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
Memory state around the buggy address:
ffffc9000ba47c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000ba47d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc9000ba47d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc9000ba47e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
syzbot
Nov 21, 2025, 1:11:35 AMNov 21
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=128d9a12580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173e7a12580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+efbf30...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
Read of size 42 at addr ffffc90003267d41 by task syz.0.17/5948
CPU: 1 PID: 5948 Comm: syz.0.17 Not tainted syzkaller #0
RAX: ffffffffffffffda RBX: 00007fee691e5fa0 RCX: 00007fee68f8f749
</TASK>
The buggy address belongs to stack of task syz.0.17/5948
memcg:ffff88807331f382
create_kthread kernel/kthread.c:411 [inline]
kthreadd+0x560/0x730 kernel/kthread.c:766
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
__slab_free+0x35e/0x410 mm/slub.c:3736
qlink_free mm/kasan/quarantine.c:166 [inline]
qlist_free_all+0x75/0xe0 mm/kasan/quarantine.c:185
kasan_quarantine_reduce+0x143/0x160 mm/kasan/quarantine.c:292
__kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6e/0x4d0 mm/slab.h:767
slab_alloc_node mm/slub.c:3495 [inline]
kmem_cache_alloc_node+0x150/0x330 mm/slub.c:3540
__alloc_skb+0x108/0x2c0 net/core/skbuff.c:640
alloc_skb include/linux/skbuff.h:1284 [inline]
nlmsg_new include/net/netlink.h:1010 [inline]
inet_netconf_notify_devconf+0x173/0x230 net/ipv4/devinet.c:2149
__devinet_sysctl_unregister net/ipv4/devinet.c:2660 [inline]
devinet_sysctl_unregister net/ipv4/devinet.c:2684 [inline]
inetdev_event+0xf0f/0x15c0 net/ipv4/devinet.c:1644
notifier_call_chain+0x197/0x390 kernel/notifier.c:93
call_netdevice_notifiers_extack net/core/dev.c:2064 [inline]
call_netdevice_notifiers net/core/dev.c:2078 [inline]
dev_change_name+0x5d4/0x8a0 net/core/dev.c:1300
do_setlink+0xa15/0x3fb0 net/core/rtnetlink.c:2885
__rtnl_newlink net/core/rtnetlink.c:3703 [inline]
rtnl_newlink+0x175b/0x2020 net/core/rtnetlink.c:3750
rtnetlink_rcv_msg+0x7c7/0xf10 net/core/rtnetlink.c:6472
Memory state around the buggy address:
ffffc90003267c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
ffffc90003267c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90003267d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc90003267d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90003267e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
HEAD commit: 0a805b6ea8cd Linux 6.6.116
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=12606d4b8832c7e4
dashboard link: https://syzkaller.appspot.com/bug?extid=efbf3074a9bd9a22b326
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=132e9742580000
dashboard link: https://syzkaller.appspot.com/bug?extid=efbf3074a9bd9a22b326
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173e7a12580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13874446b4b2/disk-0a805b6e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/69a5e59e1ade/vmlinux-0a805b6e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/322c0711f976/bzImage-0a805b6e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+efbf30...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: stack-out-of-bounds in cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
BUG: KASAN: stack-out-of-bounds in cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
CPU: 1 PID: 5948 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x220 mm/kasan/report.c:468
kasan_report+0x117/0x150 mm/kasan/report.c:581
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x288/0x290 mm/kasan/generic.c:187
__asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x888/0x1d90 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x267/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x423/0x670 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x5d1/0x7e0 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fee68f8f749
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x220 mm/kasan/report.c:468
kasan_report+0x117/0x150 mm/kasan/report.c:581
check_region_inline mm/kasan/generic.c:-1 [inline]
kasan_check_range+0x288/0x290 mm/kasan/generic.c:187
__asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
cp2112_write_req drivers/hid/hid-cp2112.c:483 [inline]
cp2112_xfer+0x714/0xf00 drivers/hid/hid-cp2112.c:698
__i2c_smbus_xfer+0x888/0x1d90 drivers/i2c/i2c-core-smbus.c:590
i2c_smbus_xfer+0x267/0x3a0 drivers/i2c/i2c-core-smbus.c:545
i2cdev_ioctl_smbus+0x423/0x670 drivers/i2c/i2c-dev.c:381
i2cdev_ioctl+0x5d1/0x7e0 drivers/i2c/i2c-dev.c:467
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:871 [inline]
__se_sys_ioctl+0xfd/0x170 fs/ioctl.c:857
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe1934d5f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007fee691e5fa0 RCX: 00007fee68f8f749
RDX: 0000200000000200 RSI: 0000000000000720 RDI: 0000000000000004
RBP: 00007fee69013f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fee691e5fa0 R14: 00007fee691e5fa0 R15: 0000000000000003
</TASK>
The buggy address belongs to stack of task syz.0.17/5948
and is located at offset 33 in frame:
i2cdev_ioctl_smbus+0x0/0x670
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to a 8-page vmalloc region starting at 0xffffc90003260000 allocated at copy_process+0x549/0x3d70 kernel/fork.c:2331
i2cdev_ioctl_smbus+0x0/0x670
This frame has 1 object:
[32, 66) 'temp'
The buggy address belongs to the physical page:
page:ffffea000071d500 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x1c754
memcg:ffff88807331f382
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 00000001ffffffff ffff88807331f382
page_type: 0xffffffff()
raw: 00fff00000000000 0000000000000000 dead000000000122 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 0x102dc2(GFP_HIGHUSER|__GFP_NOWARN|__GFP_ZERO), pid 2, tgid 2 (kthreadd), ts 72338514479, free_ts 72294243818
page_owner tracks the page as allocated
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
vm_area_alloc_pages mm/vmalloc.c:3089 [inline]
__vmalloc_area_node mm/vmalloc.c:3158 [inline]
__vmalloc_node_range+0x96b/0x1320 mm/vmalloc.c:3339
alloc_thread_stack_node kernel/fork.c:310 [inline]
dup_task_struct+0x3d0/0x7c0 kernel/fork.c:1124
copy_process+0x549/0x3d70 kernel/fork.c:2331
kernel_clone+0x21b/0x840 kernel/fork.c:2914
kernel_thread+0x10d/0x160 kernel/fork.c:2976
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
vm_area_alloc_pages mm/vmalloc.c:3089 [inline]
__vmalloc_area_node mm/vmalloc.c:3158 [inline]
__vmalloc_node_range+0x96b/0x1320 mm/vmalloc.c:3339
alloc_thread_stack_node kernel/fork.c:310 [inline]
dup_task_struct+0x3d0/0x7c0 kernel/fork.c:1124
copy_process+0x549/0x3d70 kernel/fork.c:2331
kernel_clone+0x21b/0x840 kernel/fork.c:2914
create_kthread kernel/kthread.c:411 [inline]
kthreadd+0x560/0x730 kernel/kthread.c:766
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page+0x32/0x2e0 mm/page_alloc.c:2429
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
__slab_free+0x35e/0x410 mm/slub.c:3736
qlink_free mm/kasan/quarantine.c:166 [inline]
qlist_free_all+0x75/0xe0 mm/kasan/quarantine.c:185
kasan_quarantine_reduce+0x143/0x160 mm/kasan/quarantine.c:292
__kasan_slab_alloc+0x22/0x80 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6e/0x4d0 mm/slab.h:767
slab_alloc_node mm/slub.c:3495 [inline]
kmem_cache_alloc_node+0x150/0x330 mm/slub.c:3540
__alloc_skb+0x108/0x2c0 net/core/skbuff.c:640
alloc_skb include/linux/skbuff.h:1284 [inline]
nlmsg_new include/net/netlink.h:1010 [inline]
inet_netconf_notify_devconf+0x173/0x230 net/ipv4/devinet.c:2149
__devinet_sysctl_unregister net/ipv4/devinet.c:2660 [inline]
devinet_sysctl_unregister net/ipv4/devinet.c:2684 [inline]
inetdev_event+0xf0f/0x15c0 net/ipv4/devinet.c:1644
notifier_call_chain+0x197/0x390 kernel/notifier.c:93
call_netdevice_notifiers_extack net/core/dev.c:2064 [inline]
call_netdevice_notifiers net/core/dev.c:2078 [inline]
dev_change_name+0x5d4/0x8a0 net/core/dev.c:1300
do_setlink+0xa15/0x3fb0 net/core/rtnetlink.c:2885
__rtnl_newlink net/core/rtnetlink.c:3703 [inline]
rtnl_newlink+0x175b/0x2020 net/core/rtnetlink.c:3750
rtnetlink_rcv_msg+0x7c7/0xf10 net/core/rtnetlink.c:6472
Memory state around the buggy address:
ffffc90003267c80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc90003267d00: 00 00 00 00 f1 f1 f1 f1 00 00 00 00 02 f3 f3 f3
^
ffffc90003267d80: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
ffffc90003267e00: f1 f1 f1 f1 04 f2 00 00 f2 f2 00 00 f3 f3 f3 f3
==================================================================
---
Reply all
Reply to author
Forward
0 new messages