[v5.15] KASAN: stack-out-of-bounds Read in cp2112_xfer

[syzbot]

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]

Hello,

syzbot found 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=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
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 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
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: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:

ffffc90003497c00: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f3 f3 f3
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]

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

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
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

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

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
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]

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

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
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

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

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

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

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

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
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
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

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
==================================================================


---