[v6.1] KASAN: slab-out-of-bounds Read in reg_fixed_voltage_probe
4 views
Skip to first unread message
syzbot
Aug 17, 2026, 4:26:54 PM (5 days ago) Aug 17
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c336c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=062ee723310d23496f9b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156843a60452/disk-e4f7d8be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/719d532a0151/vmlinux-e4f7d8be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12160bc2f9ec/bzImage-e4f7d8be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+062ee7...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
Read of size 4 at addr ffff88802717edac by task syz.0.325/5445
CPU: 0 PID: 5445 Comm: syz.0.325 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e 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
reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
platform_probe+0x137/0x1c0 drivers/base/platform.c:1400
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x24a/0xb40 drivers/base/dd.c:638
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:804
device_driver_attach+0xd9/0x1c0 drivers/base/dd.c:1131
bind_store+0x33b/0x380 drivers/base/bus.c:216
kernfs_fop_write_iter+0x3a0/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa08199e0d9
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:00007fa0827a9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fa081c25fa0 RCX: 00007fa08199e0d9
RDX: 000000000000000b RSI: 0000200000000700 RDI: 0000000000000003
RBP: 00007fa081a35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa081c26038 R14: 00007fa081c25fa0 R15: 00007ffcf3868198
</TASK>
Allocated by task 1:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
____kasan_kmalloc mm/kasan/common.c:375 [inline]
__kasan_kmalloc+0x8e/0xa0 mm/kasan/common.c:384
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:936 [inline]
__kmalloc_node_track_caller+0xb0/0x240 mm/slab_common.c:956
kmemdup+0x27/0x60 mm/util.c:129
kmemdup include/linux/fortify-string.h:585 [inline]
platform_device_add_data+0x2a/0xa0 drivers/base/platform.c:638
dummy_hcd_init+0x766/0x1167 drivers/usb/gadget/udc/dummy_hcd.c:2848
do_one_initcall+0x257/0x800 init/main.c:1309
do_initcall_level+0x13d/0x1ed init/main.c:1382
do_initcalls+0x4b/0x8a init/main.c:1398
kernel_init_freeable+0x401/0x5ab init/main.c:1637
kernel_init+0x19/0x1b0 init/main.c:1525
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
The buggy address belongs to the object at ffff88802717ed98
which belongs to the cache kmalloc-8 of size 8
The buggy address is located 12 bytes to the right of
8-byte region [ffff88802717ed98, ffff88802717eda0)
The buggy address belongs to the physical page:
page:ffffea00009c5f80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2717e
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 dead000000000100 dead000000000122 ffff888017441280
raw: 0000000000000000 0000000000660066 00000001ffffffff 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 0x12cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY), pid 1, tgid 1 (swapper/0), ts 9678260297, free_ts 9623161580
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2560
prep_new_page mm/page_alloc.c:2567 [inline]
get_page_from_freelist+0x206b/0x2180 mm/page_alloc.c:4358
__alloc_pages+0x1ec/0x4f0 mm/page_alloc.c:5658
alloc_page_interleave+0x24/0x1e0 mm/mempolicy.c:2115
alloc_slab_page+0x5d/0x180 mm/slub.c:1799
allocate_slab mm/slub.c:1944 [inline]
new_slab+0x87/0x2d0 mm/slub.c:1997
___slab_alloc+0xbc5/0x1240 mm/slub.c:3154
__slab_alloc mm/slub.c:3240 [inline]
slab_alloc_node mm/slub.c:3325 [inline]
__kmem_cache_alloc_node+0x126/0x270 mm/slub.c:3398
__do_kmalloc_node mm/slab_common.c:935 [inline]
__kmalloc_node_track_caller+0xa0/0x240 mm/slab_common.c:956
kvasprintf+0xe8/0x1a0 lib/kasprintf.c:25
kobject_set_name_vargs+0x5d/0x110 lib/kobject.c:265
dev_set_name+0xdf/0x130 drivers/base/core.c:3485
wiphy_new_nm+0x799/0x1a00 net/wireless/core.c:514
ieee80211_alloc_hw_nm+0x38d/0x1e80 net/mac80211/main.c:674
mac80211_hwsim_new_radio+0x143/0x4cd0 drivers/net/wireless/mac80211_hwsim.c:4260
init_mac80211_hwsim+0x598/0x737 drivers/net/wireless/mac80211_hwsim.c:5841
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1487 [inline]
free_pcp_prepare mm/page_alloc.c:1537 [inline]
free_unref_page_prepare+0x8e5/0x9e0 mm/page_alloc.c:3414
free_unref_page+0x2e/0x3f0 mm/page_alloc.c:3509
__vunmap+0x874/0xa40 mm/vmalloc.c:2726
free_work+0x56/0x80 mm/vmalloc.c:97
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Memory state around the buggy address:
ffff88802717ec80: 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 06
ffff88802717ed00: fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc
>ffff88802717ed80: fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc
^
ffff88802717ee00: fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc
ffff88802717ee80: fc 00 fc fc fc fc 00 fc fc fc fc 00 fc 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 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: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12c336c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=062ee723310d23496f9b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156843a60452/disk-e4f7d8be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/719d532a0151/vmlinux-e4f7d8be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12160bc2f9ec/bzImage-e4f7d8be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+062ee7...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
Read of size 4 at addr ffff88802717edac by task syz.0.325/5445
CPU: 0 PID: 5445 Comm: syz.0.325 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e 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
reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
platform_probe+0x137/0x1c0 drivers/base/platform.c:1400
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x24a/0xb40 drivers/base/dd.c:638
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:804
device_driver_attach+0xd9/0x1c0 drivers/base/dd.c:1131
bind_store+0x33b/0x380 drivers/base/bus.c:216
kernfs_fop_write_iter+0x3a0/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa08199e0d9
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:00007fa0827a9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fa081c25fa0 RCX: 00007fa08199e0d9
RDX: 000000000000000b RSI: 0000200000000700 RDI: 0000000000000003
RBP: 00007fa081a35024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa081c26038 R14: 00007fa081c25fa0 R15: 00007ffcf3868198
</TASK>
Allocated by task 1:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
____kasan_kmalloc mm/kasan/common.c:375 [inline]
__kasan_kmalloc+0x8e/0xa0 mm/kasan/common.c:384
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:936 [inline]
__kmalloc_node_track_caller+0xb0/0x240 mm/slab_common.c:956
kmemdup+0x27/0x60 mm/util.c:129
kmemdup include/linux/fortify-string.h:585 [inline]
platform_device_add_data+0x2a/0xa0 drivers/base/platform.c:638
dummy_hcd_init+0x766/0x1167 drivers/usb/gadget/udc/dummy_hcd.c:2848
do_one_initcall+0x257/0x800 init/main.c:1309
do_initcall_level+0x13d/0x1ed init/main.c:1382
do_initcalls+0x4b/0x8a init/main.c:1398
kernel_init_freeable+0x401/0x5ab init/main.c:1637
kernel_init+0x19/0x1b0 init/main.c:1525
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
The buggy address belongs to the object at ffff88802717ed98
which belongs to the cache kmalloc-8 of size 8
The buggy address is located 12 bytes to the right of
8-byte region [ffff88802717ed98, ffff88802717eda0)
The buggy address belongs to the physical page:
page:ffffea00009c5f80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x2717e
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 dead000000000100 dead000000000122 ffff888017441280
raw: 0000000000000000 0000000000660066 00000001ffffffff 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 0x12cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY), pid 1, tgid 1 (swapper/0), ts 9678260297, free_ts 9623161580
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2560
prep_new_page mm/page_alloc.c:2567 [inline]
get_page_from_freelist+0x206b/0x2180 mm/page_alloc.c:4358
__alloc_pages+0x1ec/0x4f0 mm/page_alloc.c:5658
alloc_page_interleave+0x24/0x1e0 mm/mempolicy.c:2115
alloc_slab_page+0x5d/0x180 mm/slub.c:1799
allocate_slab mm/slub.c:1944 [inline]
new_slab+0x87/0x2d0 mm/slub.c:1997
___slab_alloc+0xbc5/0x1240 mm/slub.c:3154
__slab_alloc mm/slub.c:3240 [inline]
slab_alloc_node mm/slub.c:3325 [inline]
__kmem_cache_alloc_node+0x126/0x270 mm/slub.c:3398
__do_kmalloc_node mm/slab_common.c:935 [inline]
__kmalloc_node_track_caller+0xa0/0x240 mm/slab_common.c:956
kvasprintf+0xe8/0x1a0 lib/kasprintf.c:25
kobject_set_name_vargs+0x5d/0x110 lib/kobject.c:265
dev_set_name+0xdf/0x130 drivers/base/core.c:3485
wiphy_new_nm+0x799/0x1a00 net/wireless/core.c:514
ieee80211_alloc_hw_nm+0x38d/0x1e80 net/mac80211/main.c:674
mac80211_hwsim_new_radio+0x143/0x4cd0 drivers/net/wireless/mac80211_hwsim.c:4260
init_mac80211_hwsim+0x598/0x737 drivers/net/wireless/mac80211_hwsim.c:5841
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1487 [inline]
free_pcp_prepare mm/page_alloc.c:1537 [inline]
free_unref_page_prepare+0x8e5/0x9e0 mm/page_alloc.c:3414
free_unref_page+0x2e/0x3f0 mm/page_alloc.c:3509
__vunmap+0x874/0xa40 mm/vmalloc.c:2726
free_work+0x56/0x80 mm/vmalloc.c:97
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Memory state around the buggy address:
ffff88802717ec80: 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 06
ffff88802717ed00: fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc
>ffff88802717ed80: fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc
^
ffff88802717ee00: fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc
ffff88802717ee80: fc 00 fc fc fc fc 00 fc fc fc fc 00 fc 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 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
Aug 19, 2026, 1:00:41 AM (3 days ago) Aug 19
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=149c7679580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17019679580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156843a60452/disk-e4f7d8be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/719d532a0151/vmlinux-e4f7d8be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12160bc2f9ec/bzImage-e4f7d8be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+062ee7...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
Read of size 4 at addr ffff888024d73cbc by task syz.0.17/4431
CPU: 1 PID: 4431 Comm: syz.0.17 Not tainted syzkaller #0
RAX: ffffffffffffffda RBX: 00007f0d62225fa0 RCX: 00007f0d61f9e0d9
RDX: 000000000000000b RSI: 0000200000000700 RDI: 0000000000000005
RBP: 00007f0d62035024 R08: 0000000000000000 R09: 0000000000000000
The buggy address belongs to the physical page:
page:ffffea0000935cc0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x24d73
kstrdup_const+0x56/0x90 mm/util.c:84
__kernfs_new_node+0xa6/0x7f0 fs/kernfs/dir.c:610
kernfs_new_node+0x148/0x250 fs/kernfs/dir.c:690
kernfs_create_link+0xa3/0x200 fs/kernfs/symlink.c:39
sysfs_do_create_link_sd+0x83/0x110 fs/sysfs/symlink.c:44
device_add_class_symlinks drivers/base/core.c:3439 [inline]
device_add+0x83b/0x1050 drivers/base/core.c:3645
device_add_disk+0x417/0xf70 block/genhd.c:470
__mmdrop+0xb0/0x480 kernel/fork.c:799
free_bprm+0x122/0x2d0 fs/exec.c:1515
kernel_execve+0x3e5/0x980 fs/exec.c:2041
call_usermodehelper_exec_async+0x207/0x350 kernel/umh.c:113
ffff888024d73c00: fc 04 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc
>ffff888024d73c80: 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00
^
ffff888024d73d00: fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc
ffff888024d73d80: fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc
==================================================================
---
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: e4f7d8be268e Linux 6.1.182
git tree: linux-6.1.y
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=062ee723310d23496f9b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1746b815580000
dashboard link: https://syzkaller.appspot.com/bug?extid=062ee723310d23496f9b
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17019679580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/156843a60452/disk-e4f7d8be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/719d532a0151/vmlinux-e4f7d8be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/12160bc2f9ec/bzImage-e4f7d8be.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+062ee7...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
CPU: 1 PID: 4431 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e 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
reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
platform_probe+0x137/0x1c0 drivers/base/platform.c:1400
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x24a/0xb40 drivers/base/dd.c:638
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:804
device_driver_attach+0xd9/0x1c0 drivers/base/dd.c:1131
bind_store+0x33b/0x380 drivers/base/bus.c:216
kernfs_fop_write_iter+0x3a0/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0d61f9e0d9
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e 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
reg_fixed_voltage_probe+0xa8b/0xd30 drivers/regulator/fixed.c:232
platform_probe+0x137/0x1c0 drivers/base/platform.c:1400
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x24a/0xb40 drivers/base/dd.c:638
__driver_probe_device+0x1f5/0x390 drivers/base/dd.c:804
device_driver_attach+0xd9/0x1c0 drivers/base/dd.c:1131
bind_store+0x33b/0x380 drivers/base/bus.c:216
kernfs_fop_write_iter+0x3a0/0x520 fs/kernfs/file.c:352
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x482/0x9a0 fs/read_write.c:584
ksys_write+0x14d/0x260 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
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:00007ffeb97975d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f0d62225fa0 RCX: 00007f0d61f9e0d9
RDX: 000000000000000b RSI: 0000200000000700 RDI: 0000000000000005
RBP: 00007f0d62035024 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f0d62225fac R14: 00007f0d62225fa0 R15: 00007f0d62225fa0
</TASK>
Allocated by task 1:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
____kasan_kmalloc mm/kasan/common.c:375 [inline]
__kasan_kmalloc+0x8e/0xa0 mm/kasan/common.c:384
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:936 [inline]
__kmalloc_node_track_caller+0xb0/0x240 mm/slab_common.c:956
kmemdup+0x27/0x60 mm/util.c:129
kmemdup include/linux/fortify-string.h:585 [inline]
platform_device_add_data+0x2a/0xa0 drivers/base/platform.c:638
dummy_hcd_init+0x766/0x1167 drivers/usb/gadget/udc/dummy_hcd.c:2848
do_one_initcall+0x257/0x800 init/main.c:1309
do_initcall_level+0x13d/0x1ed init/main.c:1382
do_initcalls+0x4b/0x8a init/main.c:1398
kernel_init_freeable+0x401/0x5ab init/main.c:1637
kernel_init+0x19/0x1b0 init/main.c:1525
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
The buggy address belongs to the object at ffff888024d73ca8
Allocated by task 1:
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
____kasan_kmalloc mm/kasan/common.c:375 [inline]
__kasan_kmalloc+0x8e/0xa0 mm/kasan/common.c:384
kasan_kmalloc include/linux/kasan.h:211 [inline]
__do_kmalloc_node mm/slab_common.c:936 [inline]
__kmalloc_node_track_caller+0xb0/0x240 mm/slab_common.c:956
kmemdup+0x27/0x60 mm/util.c:129
kmemdup include/linux/fortify-string.h:585 [inline]
platform_device_add_data+0x2a/0xa0 drivers/base/platform.c:638
dummy_hcd_init+0x766/0x1167 drivers/usb/gadget/udc/dummy_hcd.c:2848
do_one_initcall+0x257/0x800 init/main.c:1309
do_initcall_level+0x13d/0x1ed init/main.c:1382
do_initcalls+0x4b/0x8a init/main.c:1398
kernel_init_freeable+0x401/0x5ab init/main.c:1637
kernel_init+0x19/0x1b0 init/main.c:1525
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
which belongs to the cache kmalloc-8 of size 8
The buggy address is located 12 bytes to the right of
8-byte region [ffff888024d73ca8, ffff888024d73cb0)
The buggy address is located 12 bytes to the right of
The buggy address belongs to the physical page:
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 0000000000000000 dead000000000001 ffff888017441280
raw: 0000000000000000 0000000000660066 00000001ffffffff 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 0x12cc0(GFP_KERNEL|__GFP_NOWARN|__GFP_NORETRY), pid 1, tgid 1 (swapper/0), ts 8299956847, free_ts 8298990318
page dumped because: kasan: bad access detected
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:2560
prep_new_page mm/page_alloc.c:2567 [inline]
get_page_from_freelist+0x206b/0x2180 mm/page_alloc.c:4358
__alloc_pages+0x1ec/0x4f0 mm/page_alloc.c:5658
alloc_page_interleave+0x24/0x1e0 mm/mempolicy.c:2115
alloc_slab_page+0x5d/0x180 mm/slub.c:1799
allocate_slab mm/slub.c:1944 [inline]
new_slab+0x87/0x2d0 mm/slub.c:1997
___slab_alloc+0xbc5/0x1240 mm/slub.c:3154
__slab_alloc mm/slub.c:3240 [inline]
slab_alloc_node mm/slub.c:3325 [inline]
__kmem_cache_alloc_node+0x126/0x270 mm/slub.c:3398
__do_kmalloc_node mm/slab_common.c:935 [inline]
__kmalloc_node_track_caller+0xa0/0x240 mm/slab_common.c:956
kstrdup mm/util.c:61 [inline]
post_alloc_hook+0x173/0x1a0 mm/page_alloc.c:2560
prep_new_page mm/page_alloc.c:2567 [inline]
get_page_from_freelist+0x206b/0x2180 mm/page_alloc.c:4358
__alloc_pages+0x1ec/0x4f0 mm/page_alloc.c:5658
alloc_page_interleave+0x24/0x1e0 mm/mempolicy.c:2115
alloc_slab_page+0x5d/0x180 mm/slub.c:1799
allocate_slab mm/slub.c:1944 [inline]
new_slab+0x87/0x2d0 mm/slub.c:1997
___slab_alloc+0xbc5/0x1240 mm/slub.c:3154
__slab_alloc mm/slub.c:3240 [inline]
slab_alloc_node mm/slub.c:3325 [inline]
__kmem_cache_alloc_node+0x126/0x270 mm/slub.c:3398
__do_kmalloc_node mm/slab_common.c:935 [inline]
__kmalloc_node_track_caller+0xa0/0x240 mm/slab_common.c:956
kstrdup_const+0x56/0x90 mm/util.c:84
__kernfs_new_node+0xa6/0x7f0 fs/kernfs/dir.c:610
kernfs_new_node+0x148/0x250 fs/kernfs/dir.c:690
kernfs_create_link+0xa3/0x200 fs/kernfs/symlink.c:39
sysfs_do_create_link_sd+0x83/0x110 fs/sysfs/symlink.c:44
device_add_class_symlinks drivers/base/core.c:3439 [inline]
device_add+0x83b/0x1050 drivers/base/core.c:3645
device_add_disk+0x417/0xf70 block/genhd.c:470
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1487 [inline]
free_pcp_prepare mm/page_alloc.c:1537 [inline]
free_unref_page_prepare+0x8e5/0x9e0 mm/page_alloc.c:3414
free_unref_page+0x2e/0x3f0 mm/page_alloc.c:3509
mm_free_pgd kernel/fork.c:748 [inline]
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1487 [inline]
free_pcp_prepare mm/page_alloc.c:1537 [inline]
free_unref_page_prepare+0x8e5/0x9e0 mm/page_alloc.c:3414
free_unref_page+0x2e/0x3f0 mm/page_alloc.c:3509
__mmdrop+0xb0/0x480 kernel/fork.c:799
free_bprm+0x122/0x2d0 fs/exec.c:1515
kernel_execve+0x3e5/0x980 fs/exec.c:2041
call_usermodehelper_exec_async+0x207/0x350 kernel/umh.c:113
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
Memory state around the buggy address:
ffff888024d73b80: fc fc 05 fc fc fc fc 05 fc fc fc fc 05 fc fc fc
Memory state around the buggy address:
ffff888024d73c00: fc 04 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc
>ffff888024d73c80: 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00
^
ffff888024d73d00: fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc
ffff888024d73d80: fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc
==================================================================
---
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.
Reply all
Reply to author
Forward
0 new messages