KASAN: slab-out-of-bounds Write in legacy_parse_param

626 views
Skip to first unread message

syzbot

unread,
Dec 31, 2021, 7:53:17 PM12/31/21
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5b673be0c6b0 FROMGIT: USB: gadget: bRequestType is a bitfi..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=160ad1edb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8844969a6709ae53
dashboard link: https://syzkaller.appspot.com/bug?extid=02b637bea12b3944b0b9
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+02b637...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: slab-out-of-bounds in legacy_parse_param+0x4c1/0x720 fs/fs_context.c:603
Write of size 1 at addr ffff8881ee785000 by task syz-executor.5/31224

CPU: 0 PID: 31224 Comm: syz-executor.5 Not tainted 5.4.147-syzkaller-00015-g5b673be0c6b0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x18e/0x1de lib/dump_stack.c:118
print_address_description+0x9b/0x650 mm/kasan/report.c:384
__kasan_report+0x182/0x260 mm/kasan/report.c:516
kasan_report+0x30/0x60 mm/kasan/common.c:653
check_memory_region_inline mm/kasan/generic.c:141 [inline]
check_memory_region+0x2a5/0x2e0 mm/kasan/generic.c:191
memcpy+0x38/0x50 mm/kasan/common.c:124
legacy_parse_param+0x4c1/0x720 fs/fs_context.c:603
vfs_parse_fs_param+0x20f/0x430 fs/fs_context.c:145
vfs_fsconfig_locked fs/fsopen.c:265 [inline]
__do_sys_fsconfig fs/fsopen.c:445 [inline]
__se_sys_fsconfig+0xc6b/0xf40 fs/fsopen.c:314
do_syscall_64+0xcb/0x1e0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f9259b05e99
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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9258c5b168 EFLAGS: 00000246 ORIG_RAX: 00000000000001af
RAX: ffffffffffffffda RBX: 00007f9259c19030 RCX: 00007f9259b05e99
RDX: 0000000020000100 RSI: 0000000000000001 RDI: 0000000000000003
RBP: 00007f9259b5fff1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000140 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff403b9f7f R14: 00007f9258c5b300 R15: 0000000000022000

Allocated by task 31223:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
__kasan_kmalloc+0x137/0x1e0 mm/kasan/common.c:529
kmem_cache_alloc_trace+0x139/0x2b0 mm/slub.c:2849
kmalloc include/linux/slab.h:556 [inline]
legacy_parse_param+0x421/0x720 fs/fs_context.c:596
vfs_parse_fs_param+0x20f/0x430 fs/fs_context.c:145
vfs_fsconfig_locked fs/fsopen.c:265 [inline]
__do_sys_fsconfig fs/fsopen.c:445 [inline]
__se_sys_fsconfig+0xc6b/0xf40 fs/fsopen.c:314
do_syscall_64+0xcb/0x1e0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Freed by task 28036:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
kasan_set_free_info mm/kasan/common.c:345 [inline]
__kasan_slab_free+0x18a/0x240 mm/kasan/common.c:487
slab_free_hook mm/slub.c:1455 [inline]
slab_free_freelist_hook+0x7b/0x150 mm/slub.c:1493
slab_free mm/slub.c:3073 [inline]
kfree+0xe0/0x660 mm/slub.c:4064
skb_release_all net/core/skbuff.c:675 [inline]
__kfree_skb+0x55/0x170 net/core/skbuff.c:689
skb_free_datagram+0x24/0xd0 net/core/datagram.c:329
netlink_recvmsg+0x5ce/0x1060 net/netlink/af_netlink.c:1999
sock_recvmsg_nosec net/socket.c:872 [inline]
sock_recvmsg net/socket.c:890 [inline]
__sys_recvfrom+0x31d/0x490 net/socket.c:1999
__do_sys_recvfrom net/socket.c:2017 [inline]
__se_sys_recvfrom net/socket.c:2013 [inline]
__x64_sys_recvfrom+0xda/0xf0 net/socket.c:2013
do_syscall_64+0xcb/0x1e0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9

The buggy address belongs to the object at ffff8881ee784000
which belongs to the cache kmalloc-4k of size 4096
The buggy address is located 0 bytes to the right of
4096-byte region [ffff8881ee784000, ffff8881ee785000)
The buggy address belongs to the page:
page:ffffea0007b9e000 refcount:1 mapcount:0 mapping:ffff8881f5c0c280 index:0x0 compound_mapcount: 0
flags: 0x8000000000010200(slab|head)
raw: 8000000000010200 0000000000000000 0000000100000001 ffff8881f5c0c280
raw: 0000000000000000 0000000080040004 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC)
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook mm/page_alloc.c:2165 [inline]
prep_new_page+0x19a/0x380 mm/page_alloc.c:2171
get_page_from_freelist+0x550/0x8b0 mm/page_alloc.c:3794
__alloc_pages_nodemask+0x2d6/0x740 mm/page_alloc.c:4855
alloc_slab_page+0x39/0x3e0 mm/slub.c:343
allocate_slab mm/slub.c:1676 [inline]
new_slab+0x97/0x460 mm/slub.c:1742
new_slab_objects mm/slub.c:2499 [inline]
___slab_alloc+0x330/0x4c0 mm/slub.c:2660
__slab_alloc mm/slub.c:2700 [inline]
slab_alloc_node mm/slub.c:2785 [inline]
slab_alloc mm/slub.c:2830 [inline]
kmem_cache_alloc_trace+0x199/0x2b0 mm/slub.c:2847
kmalloc include/linux/slab.h:556 [inline]
kzalloc include/linux/slab.h:690 [inline]
snmp6_alloc_dev net/ipv6/addrconf.c:350 [inline]
ipv6_add_dev+0x4d1/0x1480 net/ipv6/addrconf.c:399
addrconf_notify+0x57a/0x38d0 net/ipv6/addrconf.c:3524
notifier_call_chain kernel/notifier.c:98 [inline]
__raw_notifier_call_chain kernel/notifier.c:399 [inline]
raw_notifier_call_chain+0x9e/0x110 kernel/notifier.c:406
call_netdevice_notifiers_info net/core/dev.c:1670 [inline]
call_netdevice_notifiers_extack net/core/dev.c:1682 [inline]
call_netdevice_notifiers net/core/dev.c:1696 [inline]
register_netdevice+0xdc8/0x12f0 net/core/dev.c:9196
register_netdev+0x37/0x50 net/core/dev.c:9294
sit_init_net+0x225/0x460 net/ipv6/sit.c:1866
ops_init+0x26e/0x340 net/core/net_namespace.c:137
__register_pernet_operations net/core/net_namespace.c:1146 [inline]
register_pernet_operations+0x25c/0x8e0 net/core/net_namespace.c:1223
register_pernet_device+0x2f/0x80 net/core/net_namespace.c:1310
page_owner free stack trace missing

Memory state around the buggy address:
ffff8881ee784f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881ee784f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881ee785000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8881ee785080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8881ee785100: fc fc fc fc fc fc fc fc fc fc fc fc 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.

syzbot

unread,
Dec 31, 2021, 8:08:27 PM12/31/21
to syzkaller-a...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 5b673be0c6b0 FROMGIT: USB: gadget: bRequestType is a bitfi..
git tree: android12-5.4
console output: https://syzkaller.appspot.com/x/log.txt?x=1379cb53b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=8844969a6709ae53
dashboard link: https://syzkaller.appspot.com/bug?extid=02b637bea12b3944b0b9
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172bcc95b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164707fdb00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+02b637...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: slab-out-of-bounds in legacy_parse_param+0x4c1/0x720 fs/fs_context.c:603
Write of size 92 at addr ffff8881ddd77000 by task syz-executor999/306

CPU: 1 PID: 306 Comm: syz-executor999 Not tainted 5.4.147-syzkaller-00015-g5b673be0c6b0 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x18e/0x1de lib/dump_stack.c:118
print_address_description+0x9b/0x650 mm/kasan/report.c:384
__kasan_report+0x182/0x260 mm/kasan/report.c:516
kasan_report+0x30/0x60 mm/kasan/common.c:653
check_memory_region_inline mm/kasan/generic.c:141 [inline]
check_memory_region+0x2a5/0x2e0 mm/kasan/generic.c:191
memcpy+0x38/0x50 mm/kasan/common.c:124
legacy_parse_param+0x4c1/0x720 fs/fs_context.c:603
vfs_parse_fs_param+0x20f/0x430 fs/fs_context.c:145
vfs_fsconfig_locked fs/fsopen.c:265 [inline]
__do_sys_fsconfig fs/fsopen.c:445 [inline]
__se_sys_fsconfig+0xc6b/0xf40 fs/fsopen.c:314
do_syscall_64+0xcb/0x1e0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7fc100c69939
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 a1 15 00 00 90 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 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fc100c17208 EFLAGS: 00000246 ORIG_RAX: 00000000000001af
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fc100c69939
RDX: 0000000020000280 RSI: 0000000000000001 RDI: 0000000000000003
RBP: 00007fc100cf24a0 R08: 0000000000000000 R09: 00007fc100cf24a8
R10: 00000000200000c0 R11: 0000000000000246 R12: 00007fc100cf24ac
R13: 00007ffe217a312f R14: 00007fc100c17300 R15: 0000000000022000

Allocated by task 307:
save_stack mm/kasan/common.c:70 [inline]
set_track mm/kasan/common.c:78 [inline]
__kasan_kmalloc+0x137/0x1e0 mm/kasan/common.c:529
kmem_cache_alloc_trace+0x139/0x2b0 mm/slub.c:2849
kmalloc include/linux/slab.h:556 [inline]
legacy_parse_param+0x421/0x720 fs/fs_context.c:596
vfs_parse_fs_param+0x20f/0x430 fs/fs_context.c:145
vfs_fsconfig_locked fs/fsopen.c:265 [inline]
__do_sys_fsconfig fs/fsopen.c:445 [inline]
__se_sys_fsconfig+0xc6b/0xf40 fs/fsopen.c:314
do_syscall_64+0xcb/0x1e0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x44/0xa9

Freed by task 0:
(stack is not available)

The buggy address belongs to the object at ffff8881ddd76000
which belongs to the cache kmalloc-4k of size 4096
The buggy address is located 0 bytes to the right of
4096-byte region [ffff8881ddd76000, ffff8881ddd77000)
The buggy address belongs to the page:
page:ffffea0007775c00 refcount:1 mapcount:0 mapping:ffff8881f5c0c280 index:0x0 compound_mapcount: 0
flags: 0x8000000000010200(slab|head)
raw: 8000000000010200 dead000000000100 dead000000000122 ffff8881f5c0c280
raw: 0000000000000000 0000000080040004 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC)
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook mm/page_alloc.c:2165 [inline]
prep_new_page+0x19a/0x380 mm/page_alloc.c:2171
get_page_from_freelist+0x550/0x8b0 mm/page_alloc.c:3794
__alloc_pages_nodemask+0x2d6/0x740 mm/page_alloc.c:4855
alloc_slab_page+0x39/0x3e0 mm/slub.c:343
allocate_slab mm/slub.c:1676 [inline]
new_slab+0x97/0x460 mm/slub.c:1742
new_slab_objects mm/slub.c:2499 [inline]
___slab_alloc+0x330/0x4c0 mm/slub.c:2660
__slab_alloc mm/slub.c:2700 [inline]
slab_alloc_node mm/slub.c:2785 [inline]
slab_alloc mm/slub.c:2830 [inline]
__kmalloc_track_caller+0x1d1/0x2e0 mm/slub.c:4442
__kmalloc_reserve net/core/skbuff.c:142 [inline]
__alloc_skb+0xaf/0x4d0 net/core/skbuff.c:210
alloc_skb include/linux/skbuff.h:1060 [inline]
nlmsg_new include/net/netlink.h:888 [inline]
rtmsg_ifinfo_build_skb+0x81/0x180 net/core/rtnetlink.c:3501
rtmsg_ifinfo_event net/core/rtnetlink.c:3537 [inline]
rtmsg_ifinfo+0x73/0x120 net/core/rtnetlink.c:3546
netdev_state_change+0x11a/0x1a0 net/core/dev.c:1275
linkwatch_do_dev+0xca/0x120 net/core/link_watch.c:159
__linkwatch_run_queue+0x49e/0x7a0 net/core/link_watch.c:205
linkwatch_event+0x48/0x50 net/core/link_watch.c:244
process_one_work+0x679/0x1030 kernel/workqueue.c:2278
worker_thread+0xa6f/0x1400 kernel/workqueue.c:2424
page_owner free stack trace missing

Memory state around the buggy address:
ffff8881ddd76f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8881ddd76f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8881ddd77000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8881ddd77080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff8881ddd77100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================

syzbot

unread,
Dec 31, 2021, 8:37:18 PM12/31/21
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 9b28b48fb343 Merge 5.10.89 into android12-5.10-lts
git tree: android12-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=13d0508db00000
kernel config: https://syzkaller.appspot.com/x/.config?x=194b6725650cc3e2
dashboard link: https://syzkaller.appspot.com/bug?extid=06938f44e92a5cc9d5b7
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1379bc3bb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=116efb0bb00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+06938f...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: slab-out-of-bounds in legacy_parse_param+0x5b0/0x830 fs/fs_context.c:548
Write of size 92 at addr ffff888108197000 by task syz-executor313/406

CPU: 1 PID: 406 Comm: syz-executor313 Not tainted 5.10.89-syzkaller-00788-g9b28b48fb343 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
print_address_description+0x8d/0x3d0 mm/kasan/report.c:233
__kasan_report+0x142/0x220 mm/kasan/report.c:419
kasan_report+0x51/0x70 mm/kasan/report.c:436
check_region_inline mm/kasan/generic.c:135 [inline]
kasan_check_range+0x2b6/0x2f0 mm/kasan/generic.c:186
memcpy+0x44/0x70 mm/kasan/shadow.c:66
legacy_parse_param+0x5b0/0x830 fs/fs_context.c:548
vfs_parse_fs_param+0x218/0x4d0 fs/fs_context.c:117
vfs_fsconfig_locked fs/fsopen.c:265 [inline]
__do_sys_fsconfig fs/fsopen.c:439 [inline]
__se_sys_fsconfig+0xba3/0xff0 fs/fsopen.c:314
__x64_sys_fsconfig+0xbf/0xd0 fs/fsopen.c:314
do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7f84c8542a29
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 15 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f84c84f4308 EFLAGS: 00000246 ORIG_RAX: 00000000000001af
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007f84c8542a29
RDX: 0000000020000280 RSI: 0000000000000001 RDI: 0000000000000003
RBP: 00007f84c85ca3e8 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000200000c0 R11: 0000000000000246 R12: 00007f84c85ca3e0
R13: 0073666775626564 R14: 00007f84c84f4400 R15: 0000000000022000

Allocated by task 406:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track mm/kasan/common.c:46 [inline]
set_alloc_info mm/kasan/common.c:428 [inline]
____kasan_kmalloc+0xdc/0x110 mm/kasan/common.c:507
__kasan_kmalloc+0x9/0x10 mm/kasan/common.c:516
kasan_kmalloc include/linux/kasan.h:269 [inline]
kmem_cache_alloc_trace+0x210/0x3a0 mm/slub.c:2975
kmalloc include/linux/slab.h:552 [inline]
legacy_parse_param+0x504/0x830 fs/fs_context.c:541
vfs_parse_fs_param+0x218/0x4d0 fs/fs_context.c:117
vfs_fsconfig_locked fs/fsopen.c:265 [inline]
__do_sys_fsconfig fs/fsopen.c:439 [inline]
__se_sys_fsconfig+0xba3/0xff0 fs/fsopen.c:314
__x64_sys_fsconfig+0xbf/0xd0 fs/fsopen.c:314
do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9

The buggy address belongs to the object at ffff888108196000
which belongs to the cache kmalloc-4k of size 4096
The buggy address is located 0 bytes to the right of
4096-byte region [ffff888108196000, ffff888108197000)
The buggy address belongs to the page:
page:ffffea0004206400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x108190
head:ffffea0004206400 order:3 compound_mapcount:0 compound_pincount:0
flags: 0x8000000000010200(slab|head)
raw: 8000000000010200 dead000000000100 dead000000000122 ffff888100042c00
raw: 0000000000000000 0000000080040004 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Unmovable, gfp_mask 0xd20c0(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC), pid 1, ts 962746206, free_ts 0
set_page_owner include/linux/page_owner.h:35 [inline]
post_alloc_hook mm/page_alloc.c:2385 [inline]
prep_new_page mm/page_alloc.c:2391 [inline]
get_page_from_freelist+0xa74/0xa90 mm/page_alloc.c:4063
__alloc_pages_nodemask+0x3c8/0x820 mm/page_alloc.c:5106
alloc_slab_page mm/slub.c:1807 [inline]
allocate_slab+0x6b/0x350 mm/slub.c:1809
new_slab mm/slub.c:1870 [inline]
new_slab_objects mm/slub.c:2629 [inline]
___slab_alloc+0x143/0x2f0 mm/slub.c:2792
__slab_alloc mm/slub.c:2832 [inline]
slab_alloc_node mm/slub.c:2914 [inline]
slab_alloc mm/slub.c:2956 [inline]
kmem_cache_alloc_trace+0x278/0x3a0 mm/slub.c:2973
kmalloc include/linux/slab.h:552 [inline]
kzalloc include/linux/slab.h:664 [inline]
kobject_uevent_env+0x282/0x1400 lib/kobject_uevent.c:524
kobject_uevent+0x1f/0x30 lib/kobject_uevent.c:642
device_add+0xfd4/0x1590 drivers/base/core.c:3222
device_register+0x1d/0x20 drivers/base/core.c:3314
register_memory drivers/base/memory.c:556 [inline]
init_memory_block+0x225/0x380 drivers/base/memory.c:588
add_memory_block drivers/base/memory.c:605 [inline]
memory_dev_init+0x234/0x2f8 drivers/base/memory.c:741
driver_init+0x3b/0x42 drivers/base/init.c:36
do_basic_setup+0x18/0x81 init/main.c:1314
kernel_init_freeable+0x2ba/0x3f4 init/main.c:1520
kernel_init+0x11/0x290 init/main.c:1407
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
page_owner free stack trace missing

Memory state around the buggy address:
ffff888108196f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888108196f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888108197000: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff888108197080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888108197100: fc fc fc fc fc fc fc fc fc fc fc fc 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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

Lee Jones

unread,
Jan 26, 2022, 8:04:57 AM1/26/22
to syzkaller-android-bugs
#syz fix: vfs: fs_context: fix up param length parsing in legacy_parse_param

syzbot

unread,
Jan 26, 2022, 8:05:01 AM1/26/22
to 'Lee Jones' via syzkaller-android-bugs, syzkaller-a...@googlegroups.com
> #syz fix: vfs: fs_context: fix up param length parsing in legacy_parse_param

I see the command but can't find the corresponding bug.
Please resend the email to syzbo...@syzkaller.appspotmail.com address
that is the sender of the bug report (also present in the Reported-by tag).
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-android-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-android...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-android-bugs/fed595ba-a711-4a30-81d4-23abc3033281n%40googlegroups.com.

syzbot

unread,
Apr 21, 2023, 2:01:33 PM4/21/23
to syzkaller-a...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages