KASAN: slab-out-of-bounds Read in ntfs_attr_find

Status: auto-obsoleted due to no activity on 2023/08/22 04:27
Reported-by: syzbot+2550f00760b8e9d1bf38@syzkaller.appspotmail.com
First crash: 1218d, last: 1218d
▶ ▼ Similar bugs (10)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KASAN: use-after-free Read in ntfs_attr_find ntfs3 19 syz, C done 74 1293d 1460d 22/29 fixed on 2023/02/24 13:50
upstream KASAN: slab-out-of-bounds Read in ntfs_attr_find ntfs3 17 syz, C done 9 2140d 3066d 15/29 fixed on 2020/11/16 12:12
linux-4.14 KASAN: slab-out-of-bounds Read in ntfs_attr_find 17 syz, C done 10 2133d 2161d 1/1 fixed on 2020/11/20 16:27
linux-4.14 KASAN: slab-out-of-bounds Read in ntfs_attr_find (2) 19 syz, C 31 1274d 1460d 0/1 upstream: reported C repro on 2022/08/25 11:21
linux-4.19 KASAN: slab-out-of-bounds Read in ntfs_attr_find 17 syz, C done 10 2100d 2157d 1/1 fixed on 2020/12/23 11:20
linux-5.15 KASAN: use-after-free Read in ntfs_attr_find missing-backport origin:lts-only 19 syz, C done 6 92d 947d 0/3 upstream: reported C repro on 2024/01/20 12:39
linux-6.1 KASAN: use-after-free Read in ntfs_attr_find 19 3 1219d 1230d 0/3 auto-obsoleted due to no activity on 2023/08/21 05:46
upstream KASAN: use-after-free Read in ntfs_attr_find (2) ntfs3 19 syz, C error done 22 918d 1271d 0/29 auto-obsoleted due to no activity on 2024/05/28 05:52
linux-4.19 KASAN: use-after-free Read in ntfs_attr_find (2) 19 syz, C 1 1275d 1275d 0/1 upstream: reported C repro on 2023/02/26 02:15
linux-6.1 KASAN: use-after-free Read in ntfs_attr_find (2) missing-backport origin:lts-only 19 syz, C done 3 623d 976d 0/3 upstream: reported C repro on 2023/12/22 04:54

Sample crash report:
loop1: detected capacity change from 0 to 4096
==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_attr_find+0x7d6/0xd50 fs/ntfs/attrib.c:609
Read of size 2 at addr ffff8880390fe0ae by task syz-executor.1/6622

CPU: 1 PID: 6622 Comm: syz-executor.1 Not tainted 5.15.108-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/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
 ntfs_attr_find+0x7d6/0xd50 fs/ntfs/attrib.c:609
 ntfs_attr_lookup+0x4e0/0x2390
 ntfs_read_locked_inode+0xa34/0x49c0 fs/ntfs/inode.c:666
 ntfs_read_inode_mount+0xda2/0x2660 fs/ntfs/inode.c:2098
 ntfs_fill_super+0x1a16/0x2e20 fs/ntfs/super.c:2857
 mount_bdev+0x26d/0x3a0 fs/super.c:1378
 legacy_get_tree+0xeb/0x180 fs/fs_context.c:610
 vfs_get_tree+0x88/0x270 fs/super.c:1508
 do_new_mount+0x28b/0xad0 fs/namespace.c:2994
 do_mount fs/namespace.c:3337 [inline]
 __do_sys_mount fs/namespace.c:3545 [inline]
 __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3522
 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:0x7f4b5b8a669a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 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:00007f4b59e16f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 000000000001f651 RCX: 00007f4b5b8a669a
RDX: 000000002001f6c0 RSI: 000000002001f640 RDI: 00007f4b59e16fe0
RBP: 00007f4b59e17020 R08: 00007f4b59e17020 R09: 0000000000000008
R10: 0000000000000008 R11: 0000000000000202 R12: 000000002001f6c0
R13: 000000002001f640 R14: 00007f4b59e16fe0 R15: 00000000200002c0
 </TASK>

Allocated by task 2923:
 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]
 alloc_buffer_head+0x20/0xf0 fs/buffer.c:3311
 alloc_page_buffers+0x3a3/0x660 fs/buffer.c:832
 grow_dev_page fs/buffer.c:968 [inline]
 grow_buffers fs/buffer.c:1014 [inline]
 __getblk_slow fs/buffer.c:1041 [inline]
 __getblk_gfp+0x4b4/0xaf0 fs/buffer.c:1336
 __getblk include/linux/buffer_head.h:416 [inline]
 jbd2_journal_get_descriptor_buffer+0x15a/0x440 fs/jbd2/journal.c:1020
 write_one_revoke_record fs/jbd2/revoke.c:610 [inline]
 jbd2_journal_write_revoke_records+0x440/0xa00 fs/jbd2/revoke.c:554
 jbd2_journal_commit_transaction+0x1574/0x6bb0 fs/jbd2/commit.c:598
 kjournald2+0x4ae/0x940 fs/jbd2/journal.c:213
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298

The buggy address belongs to the object at ffff8880390fe000
 which belongs to the cache buffer_head of size 168
The buggy address is located 6 bytes to the right of
 168-byte region [ffff8880390fe000, ffff8880390fe0a8)
The buggy address belongs to the page:
page:ffffea0000e43f80 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x390fe
memcg:ffff88807594d101
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 ffffea0000c9bc00 0000001400000014 ffff888012930a00
raw: 0000000000000000 0000000000110011 00000001ffffffff ffff88807594d101
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Reclaimable, gfp_mask 0x112c50(GFP_NOFS|__GFP_NOWARN|__GFP_NORETRY|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 2923, ts 300310721275, free_ts 277532450274
 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]
 alloc_buffer_head+0x20/0xf0 fs/buffer.c:3311
 jbd2_journal_write_metadata_buffer+0xec/0xb30 fs/jbd2/journal.c:364
 jbd2_journal_commit_transaction+0x1d83/0x6bb0 fs/jbd2/commit.c:711
 kjournald2+0x4ae/0x940 fs/jbd2/journal.c:213
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
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_pages_ok+0x9ef/0xaa0 mm/page_alloc.c:1643
 io_ring_ctx_free io_uring/io_uring.c:9565 [inline]
 io_ring_exit_work+0xd3d/0x1330 io_uring/io_uring.c:9718
 process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
 worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
 kthread+0x3f6/0x4f0 kernel/kthread.c:319
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298

Memory state around the buggy address:
 ffff8880390fdf80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff8880390fe000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880390fe080: 00 00 00 00 00 fc fc fc fc fc fc fc fc 00 00 00
                                  ^
 ffff8880390fe100: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff8880390fe180: 00 00 fc fc fc fc fc fc fc fc 00 00 00 00 00 00
==================================================================

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/24 04:26 linux-5.15.y 3299fb36854f 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan KASAN: slab-out-of-bounds Read in ntfs_attr_find
* Struck through repros no longer work on HEAD.