[v6.1] KASAN: use-after-free Read in reiserfs_fill_super

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 54d90d17e8ce Linux 6.1.113
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14abca40580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a9803325dabd971a
dashboard link: https://syzkaller.appspot.com/bug?extid=1f000adf424897844a29
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/640125ffcb56/disk-54d90d17.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7431c068fee3/vmlinux-54d90d17.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a421b2bfbc79/Image-54d90d17.gz.xz

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

REISERFS (device loop2): journal params: device ram0, size 127, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device loop2): checking transaction log (ram0)
==================================================================
BUG: KASAN: use-after-free in init_inode fs/reiserfs/inode.c:1317 [inline]
BUG: KASAN: use-after-free in reiserfs_read_locked_inode+0x17e8/0x1f54 fs/reiserfs/inode.c:1566
Read of size 4 at addr ffff0000f2dd6000 by task syz.2.783/6330

CPU: 0 PID: 6330 Comm: syz.2.783 Not tainted 6.1.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x174/0x4c0 mm/kasan/report.c:395
kasan_report+0xd4/0x130 mm/kasan/report.c:495
__asan_report_load_n_noabort+0x28/0x34 mm/kasan/report_generic.c:361
init_inode fs/reiserfs/inode.c:1317 [inline]
reiserfs_read_locked_inode+0x17e8/0x1f54 fs/reiserfs/inode.c:1566
reiserfs_fill_super+0x10f4/0x2028 fs/reiserfs/super.c:2071
mount_bdev+0x274/0x370 fs/super.c:1443
get_super_block+0x44/0x58 fs/reiserfs/super.c:2601
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3056
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3584
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

The buggy address belongs to the physical page:
page:000000007b898308 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x132dd6
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0003cb75c8 fffffc000389c8c8 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000f2dd5f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff0000f2dd5f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000f2dd6000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0000f2dd6080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000f2dd6100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
REISERFS warning (device loop2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [1 2 0x0 SD]. This is likely to be race with knfsd. Ignore
REISERFS warning (device loop2): reiserfs_fill_super: corrupt root inode, run fsck


---
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 report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 54d90d17e8ce Linux 6.1.113
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=15bbca40580000

kernel config: https://syzkaller.appspot.com/x/.config?x=a9803325dabd971a
dashboard link: https://syzkaller.appspot.com/bug?extid=1f000adf424897844a29
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=120a425f980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/640125ffcb56/disk-54d90d17.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7431c068fee3/vmlinux-54d90d17.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a421b2bfbc79/Image-54d90d17.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/a8ee2f54c2a6/mount_0.gz

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

==================================================================
BUG: KASAN: use-after-free in init_inode fs/reiserfs/inode.c:1317 [inline]
BUG: KASAN: use-after-free in reiserfs_read_locked_inode+0x17e8/0x1f54 fs/reiserfs/inode.c:1566

Read of size 4 at addr ffff0000f29a6000 by task syz.0.15/4466

CPU: 0 PID: 4466 Comm: syz.0.15 Not tainted 6.1.113-syzkaller #0

page:0000000044207d86 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1329a6
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0003ca69c8 ffff0001b3d11e20 0000000000000000

raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:

ffff0000f29a5f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff0000f29a5f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000f29a6000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0000f29a6080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000f29a6100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
REISERFS warning (device loop0): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [1 2 0x0 SD]. This is likely to be race with knfsd. Ignore
REISERFS warning (device loop0): reiserfs_fill_super: corrupt root inode, run fsck


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 54d90d17e8ce Linux 6.1.113
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=1747ca40580000

kernel config: https://syzkaller.appspot.com/x/.config?x=a9803325dabd971a
dashboard link: https://syzkaller.appspot.com/bug?extid=1f000adf424897844a29
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10c7ca40580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15eea0a7980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/640125ffcb56/disk-54d90d17.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7431c068fee3/vmlinux-54d90d17.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a421b2bfbc79/Image-54d90d17.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/ba176ed7aab3/mount_0.gz

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

REISERFS (device loop0): journal params: device ram0, size 127, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
REISERFS (device loop0): checking transaction log (ram0)

==================================================================
BUG: KASAN: use-after-free in init_inode fs/reiserfs/inode.c:1317 [inline]
BUG: KASAN: use-after-free in reiserfs_read_locked_inode+0x17e8/0x1f54 fs/reiserfs/inode.c:1566

Read of size 4 at addr ffff0000e5541000 by task syz-executor834/4290

CPU: 1 PID: 4290 Comm: syz-executor834 Not tainted 6.1.113-syzkaller #0

page:000000000f1bb277 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x125541
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0003955088 ffff0001b3d32e20 0000000000000000

raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:

ffff0000e5540f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff0000e5540f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000e5541000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0000e5541080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000e5541100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
REISERFS warning (device loop0): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [1 2 0x0 SD]. This is likely to be race with knfsd. Ignore
REISERFS warning (device loop0): reiserfs_fill_super: corrupt root inode, run fsck


---