[moderation] [fuse?] KASAN: slab-out-of-bounds Read in fuse_inode_eq (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4a0fc73da97e Merge tag 's390-6.6-2' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13af0af0680000
kernel config: https://syzkaller.appspot.com/x/.config?x=ed626705db308b2d
dashboard link: https://syzkaller.appspot.com/bug?extid=b5033953151c11a7efb4
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org mik...@szeredi.hu]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/feda54a5e409/disk-4a0fc73d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d3be6d41092c/vmlinux-4a0fc73d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7fd5f0bfed68/bzImage-4a0fc73d.xz

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

==================================================================
BUG: KASAN: slab-out-of-bounds in get_node_id fs/fuse/fuse_i.h:905 [inline]
BUG: KASAN: slab-out-of-bounds in fuse_inode_eq+0x54/0x70 fs/fuse/inode.c:368
Read of size 8 at addr ffff8880632f15a0 by task syz-executor.0/3851

CPU: 1 PID: 3851 Comm: syz-executor.0 Not tainted 6.5.0-syzkaller-12145-g4a0fc73da97e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0x163/0x540 mm/kasan/report.c:475
kasan_report+0x175/0x1b0 mm/kasan/report.c:588
get_node_id fs/fuse/fuse_i.h:905 [inline]
fuse_inode_eq+0x54/0x70 fs/fuse/inode.c:368
find_inode+0x16f/0x430 fs/inode.c:901
ilookup5_nowait fs/inode.c:1456 [inline]
ilookup5+0xa1/0x200 fs/inode.c:1485
iget5_locked+0x37/0x270 fs/inode.c:1266
fuse_iget+0x1cf/0x810 fs/fuse/inode.c:409
fuse_lookup_name+0x682/0x830 fs/fuse/dir.c:395
fuse_lookup+0x182/0x600 fs/fuse/dir.c:425
__lookup_slow+0x282/0x3e0 fs/namei.c:1693
lookup_slow+0x53/0x70 fs/namei.c:1710
walk_component+0x2d0/0x400 fs/namei.c:2001
lookup_last fs/namei.c:2458 [inline]
path_lookupat+0x16f/0x450 fs/namei.c:2482
filename_lookup+0x255/0x610 fs/namei.c:2511
user_path_at_empty+0x44/0x180 fs/namei.c:2910
user_path_at include/linux/namei.h:57 [inline]
__do_sys_chdir fs/open.c:551 [inline]
__se_sys_chdir+0xbf/0x220 fs/open.c:545
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f3bd4c7cae9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f3bd5a800c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000050
RAX: ffffffffffffffda RBX: 00007f3bd4d9bf80 RCX: 00007f3bd4c7cae9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 00000000200064c0
RBP: 00007f3bd4cc847a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f3bd4d9bf80 R15: 00007ffd84f0f358
</TASK>

Allocated by task 687:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4f/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x66/0x70 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:186 [inline]
slab_post_alloc_hook+0x6c/0x3b0 mm/slab.h:762
slab_alloc_node mm/slub.c:3478 [inline]
slab_alloc mm/slub.c:3486 [inline]
__kmem_cache_alloc_lru mm/slub.c:3493 [inline]
kmem_cache_alloc_lru+0x122/0x300 mm/slub.c:3509
alloc_inode_sb include/linux/fs.h:2909 [inline]
ntfs_alloc_inode+0x28/0x80 fs/ntfs3/super.c:546
alloc_inode fs/inode.c:259 [inline]
iget5_locked+0xa0/0x270 fs/inode.c:1269
ntfs_iget5+0xc6/0x38e0 fs/ntfs3/inode.c:525
ntfs_fill_super+0x2459/0x4c30 fs/ntfs3/super.c:1150
get_tree_bdev+0x416/0x5b0 fs/super.c:1577
vfs_get_tree+0x8c/0x280 fs/super.c:1750
do_new_mount+0x28f/0xae0 fs/namespace.c:3335
do_mount fs/namespace.c:3675 [inline]
__do_sys_mount fs/namespace.c:3884 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

Last potentially related work creation:
kasan_save_stack+0x3f/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xad/0xc0 mm/kasan/generic.c:492
__call_rcu_common kernel/rcu/tree.c:2653 [inline]
call_rcu+0x167/0xa70 kernel/rcu/tree.c:2767
ntfs_loadlog_and_replay+0x2dd/0x530 fs/ntfs3/fsntfs.c:326
ntfs_fill_super+0x2c51/0x4c30 fs/ntfs3/super.c:1222
get_tree_bdev+0x416/0x5b0 fs/super.c:1577
vfs_get_tree+0x8c/0x280 fs/super.c:1750
do_new_mount+0x28f/0xae0 fs/namespace.c:3335
do_mount fs/namespace.c:3675 [inline]
__do_sys_mount fs/namespace.c:3884 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

Second to last potentially related work creation:
kasan_save_stack+0x3f/0x60 mm/kasan/common.c:45
__kasan_record_aux_stack+0xad/0xc0 mm/kasan/generic.c:492
__call_rcu_common kernel/rcu/tree.c:2653 [inline]
call_rcu+0x167/0xa70 kernel/rcu/tree.c:2767
ntfs_fill_super+0x2c76/0x4c30 fs/ntfs3/super.c:1226
get_tree_bdev+0x416/0x5b0 fs/super.c:1577
vfs_get_tree+0x8c/0x280 fs/super.c:1750
do_new_mount+0x28f/0xae0 fs/namespace.c:3335
do_mount fs/namespace.c:3675 [inline]
__do_sys_mount fs/namespace.c:3884 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd

The buggy address belongs to the object at ffff8880632f0ec0
which belongs to the cache ntfs_inode_cache of size 1760
The buggy address is located 0 bytes to the right of
allocated 1760-byte region [ffff8880632f0ec0, ffff8880632f15a0)

The buggy address belongs to the physical page:
page:ffffea00018cbc00 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff8880632f2c40 pfn:0x632f0
head:ffffea00018cbc00 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
memcg:ffff888025a09501
anon flags: 0xfff00000000840(slab|head|node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000840 ffff888014b10280 0000000000000000 dead000000000001
raw: ffff8880632f2c40 000000008011000c 00000001ffffffff ffff888025a09501
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 12349, tgid 12348 (syz-executor.2), ts 368966802656, free_ts 364337302530
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1e6/0x210 mm/page_alloc.c:1536
prep_new_page mm/page_alloc.c:1543 [inline]
get_page_from_freelist+0x31db/0x3360 mm/page_alloc.c:3170
__alloc_pages+0x255/0x670 mm/page_alloc.c:4426
alloc_slab_page+0x6a/0x160 mm/slub.c:1870
allocate_slab mm/slub.c:2017 [inline]
new_slab+0x84/0x2f0 mm/slub.c:2070
___slab_alloc+0xade/0x1100 mm/slub.c:3223
__slab_alloc mm/slub.c:3322 [inline]
__slab_alloc_node mm/slub.c:3375 [inline]
slab_alloc_node mm/slub.c:3468 [inline]
slab_alloc mm/slub.c:3486 [inline]
__kmem_cache_alloc_lru mm/slub.c:3493 [inline]
kmem_cache_alloc_lru+0x1bf/0x300 mm/slub.c:3509
alloc_inode_sb include/linux/fs.h:2909 [inline]
ntfs_alloc_inode+0x28/0x80 fs/ntfs3/super.c:546
alloc_inode fs/inode.c:259 [inline]
iget5_locked+0xa0/0x270 fs/inode.c:1269
ntfs_iget5+0xc6/0x38e0 fs/ntfs3/inode.c:525
ntfs_loadlog_and_replay+0x17d/0x530 fs/ntfs3/fsntfs.c:297
ntfs_fill_super+0x2c51/0x4c30 fs/ntfs3/super.c:1222
get_tree_bdev+0x416/0x5b0 fs/super.c:1577
vfs_get_tree+0x8c/0x280 fs/super.c:1750
do_new_mount+0x28f/0xae0 fs/namespace.c:3335
do_mount fs/namespace.c:3675 [inline]
__do_sys_mount fs/namespace.c:3884 [inline]
__se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3861
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1136 [inline]
free_unref_page_prepare+0x8c3/0x9f0 mm/page_alloc.c:2312
free_unref_page+0x37/0x3f0 mm/page_alloc.c:2405
discard_slab mm/slub.c:2116 [inline]
__unfreeze_partials+0x1dc/0x220 mm/slub.c:2655
put_cpu_partial+0x116/0x180 mm/slub.c:2731
__slab_free+0x2b6/0x390 mm/slub.c:3679
qlist_free_all+0x22/0x60 mm/kasan/quarantine.c:185
kasan_quarantine_reduce+0x14b/0x160 mm/kasan/quarantine.c:292
__kasan_slab_alloc+0x23/0x70 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:186 [inline]
slab_post_alloc_hook+0x6c/0x3b0 mm/slab.h:762
slab_alloc_node mm/slub.c:3478 [inline]
__kmem_cache_alloc_node+0x141/0x270 mm/slub.c:3517
__do_kmalloc_node mm/slab_common.c:1022 [inline]
__kmalloc+0xa8/0x230 mm/slab_common.c:1036
kmalloc include/linux/slab.h:603 [inline]
tomoyo_realpath_from_path+0xcf/0x5e0 security/tomoyo/realpath.c:251
tomoyo_get_realpath security/tomoyo/file.c:151 [inline]
tomoyo_check_open_permission+0x254/0x4e0 security/tomoyo/file.c:771
security_file_open+0x63/0xa0 security/security.c:2836
do_dentry_open+0x325/0x1430 fs/open.c:916
do_open fs/namei.c:3639 [inline]
path_openat+0x27bb/0x3180 fs/namei.c:3796

Memory state around the buggy address:
ffff8880632f1480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff8880632f1500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff8880632f1580: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff8880632f1600: fc fc fc fc 00 00 00 00 00 00 00 00 00 00 00 00
ffff8880632f1680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================


---
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.