[v5.15] KASAN: use-after-free Read in jbd2_journal_get_write_access

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b911329317b4 Linux 5.15.133
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14073912680000
kernel config: https://syzkaller.appspot.com/x/.config?x=c21a1ede2e21ef2f
dashboard link: https://syzkaller.appspot.com/bug?extid=ac1ddc8b60c702c7e169
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0d67112bfdd3/disk-b9113293.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54ed715e08ee/vmlinux-b9113293.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cec49685c149/Image-b9113293.gz.xz

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

==================================================================
BUG: KASAN: use-after-free in is_handle_aborted include/linux/jbd2.h:1694 [inline]
BUG: KASAN: use-after-free in jbd2_journal_get_write_access+0x148/0x14c fs/jbd2/transaction.c:1241
Read of size 4 at addr ffff00012912fd8c by task syz-executor.0/28768

CPU: 1 PID: 28768 Comm: syz-executor.0 Not tainted 5.15.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description+0x7c/0x3f0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x174/0x1e4 mm/kasan/report.c:451
__asan_report_load4_noabort+0x44/0x50 mm/kasan/report_generic.c:308
is_handle_aborted include/linux/jbd2.h:1694 [inline]
jbd2_journal_get_write_access+0x148/0x14c fs/jbd2/transaction.c:1241
__ext4_journal_get_write_access+0x220/0x634 fs/ext4/ext4_jbd2.c:235
ext4_reserve_inode_write+0x2a8/0x328 fs/ext4/inode.c:5782
__ext4_mark_inode_dirty+0x260/0x924 fs/ext4/inode.c:5956
ext4_symlink+0x994/0xc18 fs/ext4/namei.c:3463
vfs_symlink+0x24c/0x3c8 fs/namei.c:4358
do_symlinkat+0x364/0x6b0 fs/namei.c:4387
__do_sys_symlinkat fs/namei.c:4404 [inline]
__se_sys_symlinkat fs/namei.c:4401 [inline]
__arm64_sys_symlinkat+0xa4/0xbc fs/namei.c:4401
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Allocated by task 28768:
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:434 [inline]
__kasan_slab_alloc+0x8c/0xcc mm/kasan/common.c:467
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x74/0x3f4 mm/slab.h:519
slab_alloc_node mm/slub.c:3220 [inline]
slab_alloc mm/slub.c:3228 [inline]
kmem_cache_alloc+0x1dc/0x45c mm/slub.c:3233
kmem_cache_zalloc include/linux/slab.h:711 [inline]
jbd2_alloc_handle include/linux/jbd2.h:1597 [inline]
new_handle fs/jbd2/transaction.c:477 [inline]
jbd2__journal_start+0x158/0x7b4 fs/jbd2/transaction.c:504
__ext4_journal_start_sb+0x358/0x70c fs/ext4/ext4_jbd2.c:105
__ext4_new_inode+0xf64/0x39a8 fs/ext4/ialloc.c:1080
ext4_symlink+0x408/0xc18 fs/ext4/namei.c:3382
vfs_symlink+0x24c/0x3c8 fs/namei.c:4358
do_symlinkat+0x364/0x6b0 fs/namei.c:4387
__do_sys_symlinkat fs/namei.c:4404 [inline]
__se_sys_symlinkat fs/namei.c:4401 [inline]
__arm64_sys_symlinkat+0xa4/0xbc fs/namei.c:4401
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

Freed by task 28768:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4c/0x84 mm/kasan/common.c:46
kasan_set_free_info+0x28/0x4c mm/kasan/generic.c:360
____kasan_slab_free+0x118/0x164 mm/kasan/common.c:366
__kasan_slab_free+0x18/0x28 mm/kasan/common.c:374
kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]
slab_free_freelist_hook+0x128/0x1ec mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kmem_cache_free+0xdc/0x3c4 mm/slub.c:3515
jbd2_free_handle include/linux/jbd2.h:1602 [inline]
jbd2_journal_stop+0x780/0xc78 fs/jbd2/transaction.c:1964
__ext4_journal_stop+0xe4/0x190 fs/ext4/ext4_jbd2.c:127
ext4_symlink+0x4fc/0xc18 fs/ext4/namei.c:3461
vfs_symlink+0x24c/0x3c8 fs/namei.c:4358
do_symlinkat+0x364/0x6b0 fs/namei.c:4387
__do_sys_symlinkat fs/namei.c:4404 [inline]
__se_sys_symlinkat fs/namei.c:4401 [inline]
__arm64_sys_symlinkat+0xa4/0xbc fs/namei.c:4401
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the object at ffff00012912fd68
which belongs to the cache jbd2_journal_handle of size 56
The buggy address is located 36 bytes inside of
56-byte region [ffff00012912fd68, ffff00012912fda0)
The buggy address belongs to the page:
page:000000001b07a5cf refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x16912f
flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000200 fffffc000371f280 0000000a0000000a ffff0000c0b37680
raw: 0000000000000000 00000000002e002e 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff00012912fc80: fb fb fb fc fc fc fc fa fb fb fb fb fb fb fc fc
ffff00012912fd00: fc fc fa fb fb fb fb fb fb fc fc fc fc fa fb fb
>ffff00012912fd80: fb fb fb fb fc fc fc fc fa fb fb fb fb fb fb fc
^
ffff00012912fe00: fc fc fc fa fb fb fb fb fb fb fc fc fc fc fa fb
ffff00012912fe80: fb fb fb fb fb fc fc fc fc fa fb fb fb fb fb fb
==================================================================
------------[ cut here ]------------
kernel BUG at fs/jbd2/transaction.c:1102!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 28768 Comm: syz-executor.0 Tainted: G B 5.15.133-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : do_get_write_access+0xe54/0xed8 fs/jbd2/transaction.c:1102
lr : do_get_write_access+0xe54/0xed8 fs/jbd2/transaction.c:1102
sp : ffff800021c07630
x29: ffff800021c076b0 x28: ffff0000dc7d5d88 x27: dfff800000000000
x26: 1fffe0002523761d x25: ffff0000dc7d5d20 x24: ffff0000dc7d5d90
x23: ffff0001291bb0e8 x22: 1fffe0001b8fabb2 x21: ffff0000c77e9ce0
x20: 1fffe0001b8fabaf x19: ffff0000dc3e1080 x18: 1fffe00036902f8e
x17: 1fffe00036902f8e x16: ffff800008302ff4 x15: ffff80001499efe0
x14: ffff0001b4817c80 x13: ffffffffffffffff x12: 0000000000040000
x11: 0000000000035c8b x10: ffff8000212ba000 x9 : ffff800008ec6d8c
x8 : 0000000000035c8c x7 : 0000000000000000 x6 : ffff800008ec610c
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800008ec63d4
x2 : 0000000000000000 x1 : 0000000000000008 x0 : 0000000000000000
Call trace:
do_get_write_access+0xe54/0xed8 fs/jbd2/transaction.c:1102
jbd2_journal_get_write_access+0x11c/0x14c fs/jbd2/transaction.c:1251
__ext4_journal_get_write_access+0x220/0x634 fs/ext4/ext4_jbd2.c:235
ext4_reserve_inode_write+0x2a8/0x328 fs/ext4/inode.c:5782
__ext4_mark_inode_dirty+0x260/0x924 fs/ext4/inode.c:5956
ext4_symlink+0x994/0xc18 fs/ext4/namei.c:3463
vfs_symlink+0x24c/0x3c8 fs/namei.c:4358
do_symlinkat+0x364/0x6b0 fs/namei.c:4387
__do_sys_symlinkat fs/namei.c:4404 [inline]
__se_sys_symlinkat fs/namei.c:4401 [inline]
__arm64_sys_symlinkat+0xa4/0xbc fs/namei.c:4401
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 17ffffb5 97d7ebc1 d4210000 97d7ebbf (d4210000)
---[ end trace 84eed7c5a87dda62 ]---


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: d0fc081c6241 Linux 5.15.143
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=171d7dc1e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ffd22c928742e176

dashboard link: https://syzkaller.appspot.com/bug?extid=ac1ddc8b60c702c7e169
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16cb3ffee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=159cbe7ce80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c315e9d55a2d/disk-d0fc081c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0543a2c39d86/vmlinux-d0fc081c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b6820cee1703/bzImage-d0fc081c.xz

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

RBP: 0000000000000002 R08: 00007ffee17ee586 R09: 0000000000003432
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000003
R13: 0000000000050012 R14: 00007ffee17ee8ea R15: 000000000000000d
</TASK>

==================================================================
BUG: KASAN: use-after-free in is_handle_aborted include/linux/jbd2.h:1694 [inline]

BUG: KASAN: use-after-free in jbd2_journal_get_write_access+0x12f/0x140 fs/jbd2/transaction.c:1241
Read of size 4 at addr ffff888071a53eec by task syz-executor367/3503

CPU: 0 PID: 3503 Comm: syz-executor367 Not tainted 5.15.143-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description+0x63/0x3b0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x16b/0x1c0 mm/kasan/report.c:451
is_handle_aborted include/linux/jbd2.h:1694 [inline]
jbd2_journal_get_write_access+0x12f/0x140 fs/jbd2/transaction.c:1241
__ext4_journal_get_write_access+0x257/0x6b0 fs/ext4/ext4_jbd2.c:235
ext4_reserve_inode_write+0x2bd/0x3d0 fs/ext4/inode.c:5782
__ext4_mark_inode_dirty+0x1d6/0x860 fs/ext4/inode.c:5956
ext4_symlink+0xa2f/0xed0 fs/ext4/namei.c:3463
vfs_symlink+0x2ad/0x490 fs/namei.c:4358
do_symlinkat+0x1fd/0x600 fs/namei.c:4387
__do_sys_symlink fs/namei.c:4409 [inline]
__se_sys_symlink fs/namei.c:4407 [inline]
__x64_sys_symlink+0x7a/0x90 fs/namei.c:4407
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7ff734690269
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 1f 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:00007ffee17ee7e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 00007ffee17ee7f0 RCX: 00007ff734690269
RDX: 00007ff73468f170 RSI: 0000000020000180 RDI: 0000000020000140
RBP: 0000000000000002 R08: 00007ffee17ee586 R09: 0000000000003432
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000003
R13: 0000000000050012 R14: 00007ffee17ee8ea R15: 000000000000000d
</TASK>

Allocated by task 3503:

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:434 [inline]

__kasan_slab_alloc+0x8e/0xc0 mm/kasan/common.c:467
kasan_slab_alloc include/linux/kasan.h:254 [inline]
slab_post_alloc_hook+0x53/0x380 mm/slab.h:519

slab_alloc_node mm/slub.c:3220 [inline]
slab_alloc mm/slub.c:3228 [inline]

kmem_cache_alloc+0xf3/0x280 mm/slub.c:3233

kmem_cache_zalloc include/linux/slab.h:711 [inline]
jbd2_alloc_handle include/linux/jbd2.h:1597 [inline]
new_handle fs/jbd2/transaction.c:477 [inline]

jbd2__journal_start+0x144/0x5c0 fs/jbd2/transaction.c:504
__ext4_journal_start_sb+0x175/0x370 fs/ext4/ext4_jbd2.c:105
__ext4_new_inode+0x138b/0x4430 fs/ext4/ialloc.c:1080
ext4_symlink+0x4c3/0xed0 fs/ext4/namei.c:3382
vfs_symlink+0x2ad/0x490 fs/namei.c:4358
do_symlinkat+0x1fd/0x600 fs/namei.c:4387
__do_sys_symlink fs/namei.c:4409 [inline]
__se_sys_symlink fs/namei.c:4407 [inline]
__x64_sys_symlink+0x7a/0x90 fs/namei.c:4407
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb

Freed by task 3503:
kasan_save_stack mm/kasan/common.c:38 [inline]
kasan_set_track+0x4b/0x80 mm/kasan/common.c:46
kasan_set_free_info+0x1f/0x40 mm/kasan/generic.c:360
____kasan_slab_free+0xd8/0x120 mm/kasan/common.c:366

kasan_slab_free include/linux/kasan.h:230 [inline]
slab_free_hook mm/slub.c:1705 [inline]

slab_free_freelist_hook+0xdd/0x160 mm/slub.c:1731
slab_free mm/slub.c:3499 [inline]
kmem_cache_free+0x91/0x1f0 mm/slub.c:3515
jbd2_free_handle include/linux/jbd2.h:1602 [inline]
jbd2_journal_stop+0x8d9/0xd70 fs/jbd2/transaction.c:1964
__ext4_journal_stop+0xf8/0x190 fs/ext4/ext4_jbd2.c:127
ext4_symlink+0x5fe/0xed0 fs/ext4/namei.c:3461
vfs_symlink+0x2ad/0x490 fs/namei.c:4358
do_symlinkat+0x1fd/0x600 fs/namei.c:4387
__do_sys_symlink fs/namei.c:4409 [inline]
__se_sys_symlink fs/namei.c:4407 [inline]
__x64_sys_symlink+0x7a/0x90 fs/namei.c:4407
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb

The buggy address belongs to the object at ffff888071a53ec8

which belongs to the cache jbd2_journal_handle of size 56
The buggy address is located 36 bytes inside of

56-byte region [ffff888071a53ec8, ffff888071a53f00)

The buggy address belongs to the page:

page:ffffea0001c694c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x71a53
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 0000000000000000 dead000000000122 ffff88814634d140
raw: 0000000000000000 00000000802e002e 00000001ffffffff 0000000000000000

page dumped because: kasan: bad access detected

page_owner tracks the page as allocated
page last allocated via order 0, migratetype Reclaimable, gfp_mask 0x12c50(GFP_NOFS|__GFP_NOWARN|__GFP_NORETRY|__GFP_RECLAIMABLE), pid 3492, ts 35917830207, free_ts 10187209887
prep_new_page mm/page_alloc.c:2426 [inline]
get_page_from_freelist+0x322a/0x33c0 mm/page_alloc.c:4159
__alloc_pages+0x272/0x700 mm/page_alloc.c:5421
alloc_slab_page mm/slub.c:1775 [inline]
allocate_slab mm/slub.c:1912 [inline]
new_slab+0xbb/0x4b0 mm/slub.c:1975
___slab_alloc+0x6f6/0xe10 mm/slub.c:3008
__slab_alloc mm/slub.c:3095 [inline]
slab_alloc_node mm/slub.c:3186 [inline]
slab_alloc mm/slub.c:3228 [inline]
kmem_cache_alloc+0x18e/0x280 mm/slub.c:3233

kmem_cache_zalloc include/linux/slab.h:711 [inline]
jbd2_alloc_handle include/linux/jbd2.h:1597 [inline]
new_handle fs/jbd2/transaction.c:477 [inline]

jbd2__journal_start+0x144/0x5c0 fs/jbd2/transaction.c:504
__ext4_journal_start_sb+0x175/0x370 fs/ext4/ext4_jbd2.c:105
__ext4_journal_start fs/ext4/ext4_jbd2.h:326 [inline]
ext4_dirty_inode+0x8b/0x100 fs/ext4/inode.c:5990
__mark_inode_dirty+0x2fd/0xd60 fs/fs-writeback.c:2464
mark_inode_dirty include/linux/fs.h:2436 [inline]
generic_write_end+0x232/0x440 fs/buffer.c:2204
ext4_da_write_end+0x72d/0x9e0 fs/ext4/inode.c:3084
generic_perform_write+0x3b7/0x5b0 mm/filemap.c:3787
ext4_buffered_write_iter+0x227/0x360 fs/ext4/file.c:268
ext4_file_write_iter+0x87c/0x1990
call_write_iter include/linux/fs.h:2146 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0xacf/0xe50 fs/read_write.c:594
ksys_write+0x1a2/0x2c0 fs/read_write.c:647
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1340 [inline]
free_pcp_prepare mm/page_alloc.c:1391 [inline]
free_unref_page_prepare+0xc34/0xcf0 mm/page_alloc.c:3317
free_unref_page+0x95/0x2d0 mm/page_alloc.c:3396
free_contig_range+0x95/0xf0 mm/page_alloc.c:9340
destroy_args+0xfe/0x97f mm/debug_vm_pgtable.c:1018
debug_vm_pgtable+0x40d/0x462 mm/debug_vm_pgtable.c:1331
do_one_initcall+0x22b/0x7a0 init/main.c:1299
do_initcall_level+0x157/0x207 init/main.c:1372
do_initcalls+0x49/0x86 init/main.c:1388
kernel_init_freeable+0x425/0x5b5 init/main.c:1612
kernel_init+0x19/0x290 init/main.c:1503
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298

Memory state around the buggy address:

ffff888071a53d80: fb fb fb fb fc fc fc fc fa fb fb fb fb fb fb fc
ffff888071a53e00: fc fc fc fa fb fb fb fb fb fb fc fc fc fc fa fb
>ffff888071a53e80: fb fb fb fb fb fc fc fc fc fa fb fb fb fb fb fb
^
ffff888071a53f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888071a53f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc 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.