syzbot


KASAN: use-after-free Write in ext4_insert_dentry

Status: upstream: reported C repro on 2024/09/14 11:48
Reported-by: syzbot+5371fd14aab16dddac77@syzkaller.appspotmail.com
First crash: 243d, last: 23d
Similar bugs (5)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 KASAN: use-after-free Write in ext4_insert_dentry origin:upstream missing-backport C 10 15d 200d 0/2 upstream: reported C repro on 2024/10/27 00:37
android-6-1 KASAN: use-after-free Write in ext4_insert_dentry origin:upstream missing-backport C 6 2d17h 166d 0/2 upstream: reported C repro on 2024/11/30 15:43
android-54 KASAN: use-after-free Write in ext4_insert_dentry C 7 10d 39d 0/2 upstream: reported C repro on 2025/04/06 12:10
linux-5.15 KASAN: use-after-free Write in ext4_insert_dentry origin:upstream C 4 16d 166d 0/3 upstream: reported C repro on 2024/11/29 21:09
upstream KASAN: use-after-free Write in ext4_insert_dentry ext4 C done 117 34d 201d 26/28 upstream: reported C repro on 2024/10/25 22:56
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/05/10 14:56 1h26m retest repro android13-5.10-lts OK log
2025/04/21 18:43 6m retest repro android13-5.10-lts report log
2025/04/21 18:43 11m retest repro android13-5.10-lts report log
2025/04/21 18:43 7m retest repro android13-5.10-lts report log
2025/04/21 18:43 7m retest repro android13-5.10-lts report log
2025/04/21 18:43 6m retest repro android13-5.10-lts report log
2025/04/01 08:43 14m retest repro android13-5.10-lts report log
2025/04/01 08:43 14m retest repro android13-5.10-lts report log
2025/04/01 08:43 6m retest repro android13-5.10-lts report log
2025/04/01 08:43 14m retest repro android13-5.10-lts report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2025/02/08 15:28 1h03m bisect fix android13-5.10-lts OK (0) job log log
2024/10/28 17:45 2h11m bisect fix android13-5.10-lts OK (0) job log log

Sample crash report:
EXT4-fs (loop0): mounted filesystem without journal. Opts: jqfmt=vfsold,max_batch_time=0x0000000000000001,debug,noload,nombcache,noblock_validity,init_itable=0x0000000000000601,inode_readahead_blks=0x0000000000008000,,errors=continue
==================================================================
BUG: KASAN: use-after-free in ext4_insert_dentry+0x392/0x710 fs/ext4/namei.c:2119
Write of size 248 at addr ffff888120032f28 by task syz-executor291/309

CPU: 1 PID: 309 Comm: syz-executor291 Not tainted 5.10.234-syzkaller-00033-g094fc3778d6b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
 print_address_description+0x81/0x3b0 mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:435 [inline]
 kasan_report+0x179/0x1c0 mm/kasan/report.c:452
 check_region_inline mm/kasan/generic.c:-1 [inline]
 kasan_check_range+0x293/0x2a0 mm/kasan/generic.c:189
 memcpy+0x44/0x70 mm/kasan/shadow.c:66
 ext4_insert_dentry+0x392/0x710 fs/ext4/namei.c:2119
 add_dirent_to_buf+0x3ac/0x780 fs/ext4/namei.c:2163
 make_indexed_dir+0xe9f/0x1500 fs/ext4/namei.c:2354
 ext4_add_entry+0xdcf/0x1280 fs/ext4/namei.c:2460
 ext4_add_nondir+0x97/0x270 fs/ext4/namei.c:2786
 ext4_create+0x348/0x530 fs/ext4/namei.c:2831
 lookup_open fs/namei.c:3247 [inline]
 open_last_lookups fs/namei.c:3317 [inline]
 path_openat+0x1377/0x3000 fs/namei.c:3506
 do_filp_open+0x21c/0x460 fs/namei.c:3536
 do_sys_openat2+0x13f/0x710 fs/open.c:1217
 do_sys_open fs/open.c:1233 [inline]
 __do_sys_creat fs/open.c:1309 [inline]
 __se_sys_creat fs/open.c:1303 [inline]
 __x64_sys_creat+0x11f/0x160 fs/open.c:1303
 do_syscall_64+0x34/0x70 arch/x86/entry/common.c:-1
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f6cbce50c99
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 1c 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:00007ffd42806bc8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f6cbce94616 RCX: 00007f6cbce50c99
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000300
RBP: 00007f6cbce945e6 R08: 00007ffd42806c10 R09: 00007ffd42806c10
R10: 00007ffd42806c10 R11: 0000000000000246 R12: 00007f6cbce94567
R13: 00007ffd42806c20 R14: 00007f6cbce94448 R15: 00007ffd42806c0c

The buggy address belongs to the page:
page:ffffea0004800c80 refcount:3 mapcount:0 mapping:ffff8881091a4290 index:0x3f pfn:0x120032
aops:def_blk_aops ino:0
flags: 0x400000000000202a(referenced|dirty|active|private)
raw: 400000000000202a dead000000000100 dead000000000122 ffff8881091a4290
raw: 000000000000003f ffff8881210a5690 00000003ffffffff ffff888100138000
page dumped because: kasan: bad access detected
page->mem_cgroup:ffff888100138000
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Movable, gfp_mask 0x108c48(GFP_NOFS|__GFP_NOFAIL|__GFP_HARDWALL|__GFP_MOVABLE), pid 309, ts 42972599008, free_ts 36298759709
 set_page_owner include/linux/page_owner.h:35 [inline]
 post_alloc_hook mm/page_alloc.c:2456 [inline]
 prep_new_page+0x166/0x180 mm/page_alloc.c:2462
 get_page_from_freelist+0x2d8c/0x2f30 mm/page_alloc.c:4254
 __alloc_pages_nodemask+0x435/0xaf0 mm/page_alloc.c:5348
 __alloc_pages include/linux/gfp.h:544 [inline]
 __alloc_pages_node include/linux/gfp.h:557 [inline]
 alloc_pages_node include/linux/gfp.h:571 [inline]
 alloc_pages include/linux/gfp.h:590 [inline]
 __page_cache_alloc include/linux/pagemap.h:290 [inline]
 pagecache_get_page+0x669/0x950 mm/filemap.c:1848
 find_or_create_page include/linux/pagemap.h:402 [inline]
 grow_dev_page fs/buffer.c:976 [inline]
 grow_buffers fs/buffer.c:1045 [inline]
 __getblk_slow fs/buffer.c:1072 [inline]
 __getblk_gfp+0x221/0x7e0 fs/buffer.c:1370
 sb_getblk include/linux/buffer_head.h:361 [inline]
 ext4_getblk+0x259/0x660 fs/ext4/inode.c:877
 ext4_bread+0x2f/0x1b0 fs/ext4/inode.c:922
 ext4_append+0x29a/0x4d0 fs/ext4/namei.c:83
 make_indexed_dir+0x505/0x1500 fs/ext4/namei.c:2280
 ext4_add_entry+0xdcf/0x1280 fs/ext4/namei.c:2460
 ext4_add_nondir+0x97/0x270 fs/ext4/namei.c:2786
 ext4_create+0x348/0x530 fs/ext4/namei.c:2831
 lookup_open fs/namei.c:3247 [inline]
 open_last_lookups fs/namei.c:3317 [inline]
 path_openat+0x1377/0x3000 fs/namei.c:3506
 do_filp_open+0x21c/0x460 fs/namei.c:3536
 do_sys_openat2+0x13f/0x710 fs/open.c:1217
 do_sys_open fs/open.c:1233 [inline]
 __do_sys_creat fs/open.c:1309 [inline]
 __se_sys_creat fs/open.c:1303 [inline]
 __x64_sys_creat+0x11f/0x160 fs/open.c:1303
page last free stack trace:
 reset_page_owner include/linux/page_owner.h:28 [inline]
 free_pages_prepare mm/page_alloc.c:1349 [inline]
 free_pcp_prepare mm/page_alloc.c:1421 [inline]
 free_unref_page_prepare+0x2ae/0x2d0 mm/page_alloc.c:3336
 free_unref_page_list+0x122/0xb20 mm/page_alloc.c:3443
 release_pages+0xea0/0xef0 mm/swap.c:1103
 free_pages_and_swap_cache+0x8a/0xa0 mm/swap_state.c:356
 tlb_batch_pages_flush mm/mmu_gather.c:49 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:240 [inline]
 tlb_flush_mmu mm/mmu_gather.c:247 [inline]
 tlb_finish_mmu+0x177/0x320 mm/mmu_gather.c:326
 exit_mmap+0x306/0x560 mm/mmap.c:3375
 __mmput+0x95/0x2d0 kernel/fork.c:1153
 mmput+0x59/0x170 kernel/fork.c:1176
 exit_mm kernel/exit.c:539 [inline]
 do_exit+0xbda/0x2a50 kernel/exit.c:850
 do_group_exit+0x141/0x310 kernel/exit.c:985
 __do_sys_exit_group kernel/exit.c:996 [inline]
 __se_sys_exit_group kernel/exit.c:994 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:994
 do_syscall_64+0x34/0x70 arch/x86/entry/common.c:-1
 entry_SYSCALL_64_after_hwframe+0x61/0xcb

Memory state around the buggy address:
 ffff888120032f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888120032f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888120033000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff888120033080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888120033100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================

Crashes (25):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/04/07 05:00 android13-5.10-lts 094fc3778d6b 1c65791e .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/18 07:53 android13-5.10-lts 094fc3778d6b ce3352cd .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/18 07:16 android13-5.10-lts 094fc3778d6b ce3352cd .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/16 23:40 android13-5.10-lts fc9aa81462ee e2826670 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/16 22:17 android13-5.10-lts fc9aa81462ee e2826670 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/16 21:16 android13-5.10-lts fc9aa81462ee e2826670 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/16 19:26 android13-5.10-lts fc9aa81462ee e2826670 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/03/16 18:56 android13-5.10-lts fc9aa81462ee e2826670 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/02/28 12:16 android13-5.10-lts 3f5f2283d684 6a8fcbc4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/02/25 17:03 android13-5.10-lts 3f5f2283d684 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/02/25 14:51 android13-5.10-lts 3f5f2283d684 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/02/25 13:25 android13-5.10-lts 3f5f2283d684 d34966d1 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/02/25 12:33 android13-5.10-lts 3f5f2283d684 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2025/02/25 11:43 android13-5.10-lts 3f5f2283d684 d34966d1 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/26 18:38 android13-5.10-lts 139a6bb26d9d e9a9a9f2 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/27 02:17 android13-5.10-lts 139a6bb26d9d e9a9a9f2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/27 02:01 android13-5.10-lts 139a6bb26d9d e9a9a9f2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/25 07:00 android13-5.10-lts b14940b90491 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/25 07:00 android13-5.10-lts b14940b90491 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/25 07:00 android13-5.10-lts b14940b90491 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/23 13:55 android13-5.10-lts b14940b90491 68da6d95 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/22 20:22 android13-5.10-lts b14940b90491 4b25d554 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/21 18:07 android13-5.10-lts b14940b90491 4b25d554 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/11/02 18:44 android13-5.10-lts e5e5644ea27f f00eed24 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
2024/09/14 11:47 android13-5.10-lts 8d23314f588a c7e35043 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-android-5-10 KASAN: use-after-free Write in ext4_insert_dentry
* Struck through repros no longer work on HEAD.