syzbot


corrupted report (3)

Status: premoderation: reported on 2024/04/08 19:56
Reported-by: syzbot+cd46a6f5ac3b55c51494@syzkaller.appspotmail.com
First crash: 727d, last: 3h17m
Similar bugs (23)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 corrupted report (2) -1 6 945d 1023d 0/2 auto-obsoleted due to no activity on 2023/12/02 13:09
android-54 corrupted report (2) -1 105976 314d 435d 0/2 auto-obsoleted due to no activity on 2025/07/15 11:08
linux-4.19 corrupted report gfs2 sysv ext4 hfsplus -1 6619 1126d 2551d 0/1 upstream: reported on 2019/04/11 04:14
android-414 corrupted report -1 5888 2317d 2552d 0/1 auto-closed as invalid on 2020/02/29 14:20
android-5-15 corrupted report -1 4 994d 1076d 0/2 auto-obsoleted due to no activity on 2023/10/14 13:19
android-6-12 corrupted report -1 191 142d 287d 0/1 auto-obsoleted due to no activity on 2026/01/03 01:56
linux-6.6 corrupted report -1 7543 34m 293d 0/2 upstream: reported on 2025/06/16 23:08
upstream corrupted report -1 29 3054d 3056d 0/29 closed as invalid on 2017/11/24 12:19
android-54 corrupted report -1 860856 615d 2246d 0/2 auto-obsoleted due to no activity on 2024/10/07 14:17
linux-4.4 corrupted report -1 12 2397d 2525d 0/1 auto-closed as invalid on 2020/01/10 12:28
android-6-12 corrupted report (2) -1 710 56m 74d 0/1 premoderation: reported on 2026/01/21 07:36
linux-4.14 corrupted report cramfs -1 6026 1126d 2550d 0/1 upstream: reported on 2019/04/12 21:21
android-6-1 corrupted report -1 329 2h45m 985d 0/2 premoderation: reported on 2023/07/25 23:06
android-5-15 corrupted report (3) -1 71 507d 733d 0/2 auto-obsoleted due to no activity on 2025/01/03 14:55
android-5-10 corrupted report -1 289 1424d 1573d 0/2 auto-closed as invalid on 2022/07/11 05:59
android-49 corrupted report -1 567 3054d 3056d 0/3 closed as invalid on 2017/11/24 12:19
android-5-15 corrupted report (4) -1 167 2d06h 449d 0/2 premoderation: reported on 2025/01/11 16:11
android-5-15 corrupted report (2) -1 1 855d 855d 0/2 auto-obsoleted due to no activity on 2024/03/01 04:17
upstream corrupted report (2) mm block -1 1092426 now 2916d 0/29 moderation: reported on 2018/04/11 09:52
linux-5.15 corrupted report -1 9317 2h26m 1120d 0/3 upstream: reported on 2023/03/12 22:30
android-49 corrupted report (2) -1 19181 2314d 2548d 0/3 auto-closed as invalid on 2020/03/03 12:39
linux-6.1 corrupted report -1 188350 now 1125d 0/3 upstream: reported on 2023/03/07 17:14
android-44 corrupted report -1 7075 2315d 2548d 0/2 auto-closed as invalid on 2020/03/02 23:26

Sample crash report:
==================================================================
BUG: KASAN: out-of-bounds in ext4_xattr_set_entry+0x1d79/0x3860 fs/ext4/xattr.c:1708
Read of size 18446744073709550624 at addr ffff88810e2c77e0 by task syz.7.548/2619

CPU: 0 PID: 2619 Comm: syz.7.548 Tainted: G        W         syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 __dump_stack+0x21/0x24 lib/dump_stack.c:77
 dump_stack_lvl+0x1a7/0x208 lib/dump_stack.c:118
 print_address_description+0x7f/0x2c0 mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:435 [inline]
 kasan_report+0xe2/0x130 mm/kasan/report.c:452
 check_region_inline mm/kasan/generic.c:-1 [inline]
 kasan_check_range+0x249/0x2a0 mm/kasan/generic.c:189
 memmove+0x2d/0x70 mm/kasan/shadow.c:54
 ext4_xattr_set_entry+0x1d79/0x3860 fs/ext4/xattr.c:1708
 ext4_xattr_block_set+0x4e0/0x2a80 fs/ext4/xattr.c:1916
 ext4_xattr_set_handle+0xbc4/0x12b0 fs/ext4/xattr.c:2398
 ext4_xattr_set+0x1f4/0x310 fs/ext4/xattr.c:2499
 ext4_xattr_trusted_set+0x3b/0x50 fs/ext4/xattr_trusted.c:37
 __vfs_setxattr+0x42a/0x480 fs/xattr.c:177
 __vfs_setxattr_noperm+0x11e/0x4e0 fs/xattr.c:208
 __vfs_setxattr_locked+0x203/0x220 fs/xattr.c:266
 vfs_setxattr+0x8d/0x1c0 fs/xattr.c:283
 setxattr+0x1df/0x3f0 fs/xattr.c:548
 path_setxattr+0x11f/0x230 fs/xattr.c:567
 __do_sys_lsetxattr fs/xattr.c:589 [inline]
 __se_sys_lsetxattr fs/xattr.c:585 [inline]
 __x64_sys_lsetxattr+0xc2/0xe0 fs/xattr.c:585
 do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
 entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fbd7c648819
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:00007fbd7b082028 EFLAGS: 00000246 ORIG_RAX: 00000000000000bd
RAX: ffffffffffffffda RBX: 00007fbd7c8c2090 RCX: 00007fbd7c648819
RDX: 0000200000000380 RSI: 0000200000000100 RDI: 0000200000000040
RBP: 00007fbd7c6dec91 R08: 0000000000000000 R09: 0000000000000000
R10: 000000000000fe37 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fbd7c8c2128 R14: 00007fbd7c8c2090 R15: 00007ffc815e2cb8

The buggy address belongs to the page:
page:ffffea000438b1c0 refcount:2 mapcount:0 mapping:ffff888110344b10 index:0x1c pfn:0x10e2c7
aops:def_blk_aops ino:0
flags: 0x400000000000203a(referenced|dirty|lru|active|private)
raw: 400000000000203a ffffea0004c831c8 ffffea00044f6288 ffff888110344b10
raw: 000000000000001c ffff88810d38c498 00000002ffffffff ffff8881113a2000
page dumped because: kasan: bad access detected
page->mem_cgroup:ffff8881113a2000
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 2604, ts 104046082962, free_ts 104019922543
 set_page_owner include/linux/page_owner.h:35 [inline]
 post_alloc_hook mm/page_alloc.c:2456 [inline]
 prep_new_page+0x179/0x180 mm/page_alloc.c:2462
 get_page_from_freelist+0x223b/0x23d0 mm/page_alloc.c:4254
 __alloc_pages_nodemask+0x290/0x620 mm/page_alloc.c:5384
 __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+0x63e/0x930 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+0x212/0x780 fs/buffer.c:1370
 sb_getblk include/linux/buffer_head.h:361 [inline]
 ext4_xattr_block_set+0x1ccc/0x2a80 fs/ext4/xattr.c:2097
 ext4_xattr_set_handle+0xbc4/0x12b0 fs/ext4/xattr.c:2398
 ext4_xattr_set+0x1f4/0x310 fs/ext4/xattr.c:2499
 ext4_xattr_user_set+0xc9/0xf0 fs/ext4/xattr_user.c:40
 __vfs_setxattr+0x42a/0x480 fs/xattr.c:177
 __vfs_setxattr_noperm+0x11e/0x4e0 fs/xattr.c:208
 __vfs_setxattr_locked+0x203/0x220 fs/xattr.c:266
 vfs_setxattr+0x8d/0x1c0 fs/xattr.c:283
 setxattr+0x1df/0x3f0 fs/xattr.c:548
 path_setxattr+0x11f/0x230 fs/xattr.c:567
 __do_sys_setxattr fs/xattr.c:582 [inline]
 __se_sys_setxattr fs/xattr.c:578 [inline]
 __x64_sys_setxattr+0xc5/0xe0 fs/xattr.c:578
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+0x2b7/0x2d0 mm/page_alloc.c:3336
 free_unref_page_list+0x129/0x9c0 mm/page_alloc.c:3443
 release_pages+0xe52/0xea0 mm/swap.c:1103
 __pagevec_release+0x71/0xe0 mm/swap.c:1123
 pagevec_release include/linux/pagevec.h:88 [inline]
 shmem_undo_range+0x74a/0x1810 mm/shmem.c:965
 shmem_truncate_range mm/shmem.c:1069 [inline]
 shmem_evict_inode+0x210/0xa00 mm/shmem.c:1169
 evict+0x4ae/0x930 fs/inode.c:612
 iput_final fs/inode.c:1736 [inline]
 iput+0x638/0x7c0 fs/inode.c:1762
 dentry_unlink_inode+0x2cf/0x380 fs/dcache.c:378
 __dentry_kill+0x44f/0x650 fs/dcache.c:583
 dentry_kill+0xc0/0x2a0 fs/dcache.c:-1
 dput+0x42/0x80 fs/dcache.c:883
 __fput+0x4fe/0x770 fs/file_table.c:294
 ____fput+0x15/0x20 fs/file_table.c:314
 task_work_run+0x127/0x190 kernel/task_work.c:189
 tracehook_notify_resume include/linux/tracehook.h:188 [inline]
 exit_to_user_mode_loop+0xcb/0xe0 kernel/entry/common.c:172

Memory state around the buggy address:
 ffff88810e2c7680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88810e2c7700: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88810e2c7780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                                                       ^
 ffff88810e2c7800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff88810e2c7880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================

Crashes (102):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/04/05 22:31 android13-5.10-lts cc0ae2abdc73 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/04/04 08:31 android13-5.10-lts cc0ae2abdc73 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/04/03 17:44 android13-5.10-lts cc0ae2abdc73 4440e7c2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/03/21 05:31 android13-5.10-lts 9136079e403a 5b92003d .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/03/17 00:55 android13-5.10-lts 9136079e403a 0737c18f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/03/16 21:48 android13-5.10-lts 9136079e403a 0737c18f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/03/12 12:44 android13-5.10-lts 9136079e403a 4efadf07 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/03/01 01:46 android13-5.10-lts dad37bbb13a8 43249bac .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/02/25 12:39 android13-5.10-lts e8b14e1cefe8 94a9671e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/02/13 03:54 android13-5.10-lts e8b14e1cefe8 504cb1bf .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/02/12 07:05 android13-5.10-lts ee0977df88b5 76a109e2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/01/31 19:17 android13-5.10-lts 186f761c519d afc0c4d4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2026/01/24 00:28 android13-5.10-lts 5601baec60aa 4f25b9b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/01/21 08:42 android13-5.10-lts e253c52bbdfc 6f1aa2f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2026/01/09 13:50 android13-5.10-lts e253c52bbdfc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2026/01/08 18:04 android13-5.10-lts e253c52bbdfc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/11/22 00:32 android13-5.10-lts e625d26dbfea 4fb8ef37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/11/20 04:33 android13-5.10-lts ab3e1c0dd1ff 26ee5237 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/11/04 22:39 android13-5.10-lts ab3e1c0dd1ff 686bf657 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/11/03 15:27 android13-5.10-lts ab3e1c0dd1ff 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/10/30 15:01 android13-5.10-lts ab3e1c0dd1ff fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/10/29 22:31 android13-5.10-lts 2ece552169c2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/10/28 03:12 android13-5.10-lts 2ece552169c2 fd2207e7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/10/27 03:29 android13-5.10-lts 2ece552169c2 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/10/15 04:08 android13-5.10-lts 2ece552169c2 b6605ba8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/10/09 18:01 android13-5.10-lts 2ece552169c2 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/10/01 06:35 android13-5.10-lts 0a91f603159e 65a0eece .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/09/30 10:26 android13-5.10-lts 0a91f603159e 86341da6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/09/29 06:53 android13-5.10-lts 911f602c2237 001c9061 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/09/26 12:02 android13-5.10-lts 911f602c2237 0abd0691 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/09/21 09:16 android13-5.10-lts 911f602c2237 67c37560 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/09/18 22:06 android13-5.10-lts 911f602c2237 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/09/02 02:01 android13-5.10-lts 1154f779f3f3 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/08/25 21:30 android13-5.10-lts 1154f779f3f3 bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/07/13 04:44 android13-5.10-lts 59e9a7228857 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/07/11 21:45 android13-5.10-lts 59e9a7228857 3cda49cf .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/29 08:05 android13-5.10-lts 59e9a7228857 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/28 12:49 android13-5.10-lts 59e9a7228857 fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/27 07:00 android13-5.10-lts 59e9a7228857 803ce19b .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/11 11:36 android13-5.10-lts d76d4cd0623a 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/11 02:38 android13-5.10-lts d76d4cd0623a 5d7e17ca .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/09 20:00 android13-5.10-lts d76d4cd0623a 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
2025/06/08 21:26 android13-5.10-lts d76d4cd0623a 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/06 23:23 android13-5.10-lts d76d4cd0623a 9fa58bba .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10 corrupted report
2025/06/03 03:37 android13-5.10-lts cf6ed0f1511d a30356b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-android-5-10-perf corrupted report
* Struck through repros no longer work on HEAD.