syzbot

 sign-in | mailing list | source | docs
🐞 Open [976] ≡ Subsystems 🐞 Fixed [5235] 🐞 Invalid [12491] ⬇ Missing Backports [83] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

KASAN: stack-out-of-bounds Read in iput

Status: auto-obsoleted due to no activity on 2023/10/05 12:37
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+870ae3a4c7a251c996bd@syzkaller.appspotmail.com
First crash: 581d, last: 300d
Cause bisection: introduced by (bisect log) [no-op commit]:
commit 400a5e5f15a6a64bd4aed59af703efe748a8778a
Author: Louis Peens <louis.peens@corigine.com>
Date: Thu Jul 22 07:58:07 2021 +0000

  nfp: flower-ct: add offload calls to the nfp

Crash: BUG: sleeping function called from invalid context in lock_sock_nested (log)
Repro: C syz .config
  
Fix bisection: fixed by (bisect log) :
commit c1b05105573b2cd5845921eb0d2caa26e2144a34
Author: Jakub Kicinski <kuba@kernel.org>
Date: Wed Nov 9 18:32:54 2022 +0000

  genetlink: fix single op policy dump when do is present

  
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] KASAN: stack-out-of-bounds Read in iput 1 (3) 2023/09/10 01:56
▶ ▼ Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 BUG: Dentry still in use in unmount C done 1184 789d 802d 2/2 fixed on 2022/02/25 03:20
android-54 BUG: Dentry still in use [unmount of ramfs ramfs] C 476 808d 1131d 0/2 auto-obsoleted due to no activity on 2023/04/21 02:49
upstream KASAN: use-after-free Read in iput (2) gfs2 6 1043d 1247d 0/26 auto-closed as invalid on 2021/10/12 21:28
▶ ▼ Last patch testing requests (2)
Created Duration User Patch Repo Result
2023/09/05 14:21 22m retest repro upstream OK log
2023/08/29 08:17 10m retest repro upstream report log
▶ ▼ Fix bisection attempts (8)
Created Duration User Patch Repo Result
2023/09/09 19:40 6h13m bisect fix upstream job log (1)
2023/06/27 11:32 1h05m bisect fix upstream job log (0) log
2023/05/27 10:12 58m bisect fix upstream job log (0) log
2023/04/23 00:15 53m bisect fix upstream job log (0) log
2023/03/23 21:45 2h12m bisect fix upstream job log (0) log
2023/02/21 13:22 52m bisect fix upstream job log (0) log
2023/01/21 11:31 49m bisect fix upstream job log (0) log
2022/11/04 15:13 49m bisect fix upstream job log (0) log

Sample crash report:
ntfs3: loop2: RAW NTFS volume: Filesystem size 0.00 Gb > volume size 0.00 Gb. Mount in read-only
==================================================================
BUG: KASAN: stack-out-of-bounds in native_save_fl arch/x86/include/asm/irqflags.h:35 [inline]
BUG: KASAN: stack-out-of-bounds in arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
BUG: KASAN: stack-out-of-bounds in arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
BUG: KASAN: stack-out-of-bounds in lock_acquire+0x1c3/0x3c0 kernel/locking/lockdep.c:5669
Read of size 8 at addr ffffc9000b7df95f by task syz-executor383/13922

CPU: 0 PID: 13922 Comm: syz-executor383 Not tainted 6.0.0-rc6-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
 print_address_description+0x65/0x4b0 mm/kasan/report.c:317
 print_report+0x108/0x1f0 mm/kasan/report.c:433
 kasan_report+0xc3/0xf0 mm/kasan/report.c:495
 native_save_fl arch/x86/include/asm/irqflags.h:35 [inline]
 arch_local_save_flags arch/x86/include/asm/irqflags.h:70 [inline]
 arch_irqs_disabled arch/x86/include/asm/irqflags.h:130 [inline]
 lock_acquire+0x1c3/0x3c0 kernel/locking/lockdep.c:5669
 __raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
 _raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
 spin_lock include/linux/spinlock.h:349 [inline]
 iput_final fs/inode.c:1737 [inline]
 iput+0x3ee/0x760 fs/inode.c:1774
 ntfs_fill_super+0x2352/0x42a0 fs/ntfs3/super.c:1278
 get_tree_bdev+0x400/0x620 fs/super.c:1323
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 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+0x63/0xcd
RIP: 0033:0x7f203d446d7a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 d8 00 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 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:00007f203d3f1078 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f203d3f10d0 RCX: 00007f203d446d7a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f203d3f1090
RBP: 000000000000000e R08: 00007f203d3f10d0 R09: 00007f203d3f16b8
R10: 0000000000000000 R11: 0000000000000286 R12: 00007f203d3f1090
R13: 0000000020000350 R14: 0000000000000003 R15: 0000000000000004
 </TASK>

The buggy address belongs to stack of task syz-executor383/13922
 and is located at offset 31 in frame:
 lock_acquire+0x0/0x3c0 kernel/locking/lockdep.c:5621

This frame has 3 objects:
 [32, 40) 'flags.i.i.i87'
 [64, 72) 'flags.i.i.i'
 [96, 136) 'hlock'

The buggy address belongs to the virtual mapping at
 [ffffc9000b7d8000, ffffc9000b7e1000) created by:
 dup_task_struct+0x8b/0x490 kernel/fork.c:977

The buggy address belongs to the physical page:
page:ffffea0001bcb8c0 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x6f2e3
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 0000000000000000 dead000000000122 0000000000000000
raw: 0000000000000000 0000000000000000 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 0x2dc2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN|__GFP_ZERO), pid 3629, tgid 3629 (syz-executor383), ts 473162860658, free_ts 11190855215
 prep_new_page mm/page_alloc.c:2532 [inline]
 get_page_from_freelist+0x742/0x7c0 mm/page_alloc.c:4283
 __alloc_pages+0x259/0x560 mm/page_alloc.c:5515
 vm_area_alloc_pages mm/vmalloc.c:2958 [inline]
 __vmalloc_area_node mm/vmalloc.c:3026 [inline]
 __vmalloc_node_range+0x8f4/0x1290 mm/vmalloc.c:3196
 alloc_thread_stack_node+0x307/0x500 kernel/fork.c:312
 dup_task_struct+0x8b/0x490 kernel/fork.c:977
 copy_process+0x65b/0x3fd0 kernel/fork.c:2088
 kernel_clone+0x21f/0x790 kernel/fork.c:2674
 __do_sys_clone kernel/fork.c:2808 [inline]
 __se_sys_clone kernel/fork.c:2792 [inline]
 __x64_sys_clone+0x228/0x290 kernel/fork.c:2792
 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+0x63/0xcd
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:24 [inline]
 free_pages_prepare mm/page_alloc.c:1449 [inline]
 free_pcp_prepare+0x812/0x900 mm/page_alloc.c:1499
 free_unref_page_prepare mm/page_alloc.c:3380 [inline]
 free_unref_page+0x7d/0x5f0 mm/page_alloc.c:3476
 free_contig_range+0xa3/0x160 mm/page_alloc.c:9408
 destroy_args+0xfe/0x91d mm/debug_vm_pgtable.c:1031
 debug_vm_pgtable+0x43e/0x497 mm/debug_vm_pgtable.c:1354
 do_one_initcall+0x1b9/0x3e0 init/main.c:1296
 do_initcall_level+0x168/0x218 init/main.c:1369
 do_initcalls+0x4b/0x8c init/main.c:1385
 kernel_init_freeable+0x3f1/0x57b init/main.c:1623
 kernel_init+0x19/0x2b0 init/main.c:1512
 ret_from_fork+0x1f/0x30

Memory state around the buggy address:
 ffffc9000b7df800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffffc9000b7df880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000b7df900: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f2 f2 f2
                                                    ^
 ffffc9000b7df980: 00 f2 f2 f2 00 00 00 00 00 f3 f3 f3 f3 f3 f3 f3
 ffffc9000b7dfa00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Crashes (10):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/09/19 17:48 upstream 521a547ced64 dd9a85ff .config console log report syz C [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/09/25 15:50 upstream 105a36f3694e 0042f2b4 .config console log report syz [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/10/03 14:02 upstream a962b54e162c feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/10/02 06:40 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/10/02 02:41 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/10/01 21:46 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/10/01 14:22 upstream ffb4d94b4314 feb56351 .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/09/25 21:02 upstream 105a36f3694e 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/09/19 21:36 upstream 521a547ced64 dd9a85ff .config console log report info [disk image] [vmlinux] ci2-upstream-fs KASAN: stack-out-of-bounds Read in iput
2022/09/29 14:33 upstream c3e0e1e23c70 45fd7169 .config console log report info [disk image] [vmlinux] ci2-upstream-fs BUG: unable to handle kernel paging request in iput
* Struck through repros no longer work on HEAD.