[Android 6.1] KASAN: use-after-free Read in ext4_read_inline_dir (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e2b9748880b9 ANDROID: ABI: update symbol list for honor
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=16e89af8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f475bced78b11d3
dashboard link: https://syzkaller.appspot.com/bug?extid=ac63730e8e5e21567ff1
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127b9818580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d216df980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7e18049cdcb8/disk-e2b97488.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/73b4f83b4061/vmlinux-e2b97488.xz
kernel image: https://storage.googleapis.com/syzbot-assets/aacbc9887a72/bzImage-e2b97488.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/6168f7d241f2/mount_0.gz

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

==================================================================
BUG: KASAN: use-after-free in ext4_read_inline_data fs/ext4/inline.c:210 [inline]
BUG: KASAN: use-after-free in ext4_read_inline_dir+0x48c/0xf60 fs/ext4/inline.c:1512
Read of size 68 at addr ffff888126c3dd05 by task syz-executor425/292

CPU: 1 PID: 292 Comm: syz-executor425 Not tainted 6.1.118-syzkaller-00078-ge2b9748880b9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:316 [inline]
print_report+0x158/0x4e0 mm/kasan/report.c:427
kasan_report+0x13c/0x170 mm/kasan/report.c:531
kasan_check_range+0x294/0x2a0 mm/kasan/generic.c:189
memcpy+0x2d/0x70 mm/kasan/shadow.c:65
ext4_read_inline_data fs/ext4/inline.c:210 [inline]
ext4_read_inline_dir+0x48c/0xf60 fs/ext4/inline.c:1512
ext4_readdir+0x3d1/0x3860 fs/ext4/dir.c:158
iterate_dir+0x265/0x600
__do_sys_getdents64 fs/readdir.c:369 [inline]
__se_sys_getdents64+0x1c1/0x460 fs/readdir.c:354
__x64_sys_getdents64+0x7b/0x90 fs/readdir.c:354
x64_sys_call+0x5ae/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7ff1154c6753
Code: c1 66 0f 1f 44 00 00 48 83 c4 08 48 89 ef 5b 5d e9 d2 12 fb ff 66 90 b8 ff ff ff 7f 48 39 c2 48 0f 47 d0 b8 d9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 c7 c2 b8 ff ff ff f7 d8
RSP: 002b:00007ffc14c8a6e8 EFLAGS: 00000293 ORIG_RAX: 00000000000000d9
RAX: ffffffffffffffda RBX: 00005555700aa870 RCX: 00007ff1154c6753
RDX: 0000000000008000 RSI: 00005555700aa870 RDI: 0000000000000005
RBP: 00005555700aa844 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000293 R12: ffffffffffffffb8
R13: 0000000000000016 R14: 00005555700aa840 R15: 0000000000000001
</TASK>

The buggy address belongs to the physical page:
page:ffffea00049b0f40 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x126c3d
flags: 0x4000000000000000(zone=1)
raw: 4000000000000000 ffffea00049b0f88 ffffea00049b0f08 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)

Memory state around the buggy address:
ffff888126c3dc00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888126c3dc80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888126c3dd00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff888126c3dd80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff888126c3de00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
EXT4-fs error (device loop0): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor425: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0
EXT4-fs error (device loop0): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor425: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0
EXT4-fs error (device loop0): empty_inline_dir:1877: inode #12: block 5: comm syz-executor425: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs error (device loop0): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor425: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0
EXT4-fs error (device loop0): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor425: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0
EXT4-fs error (device loop0): empty_inline_dir:1877: inode #12: block 5: comm syz-executor425: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs error (device loop0): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor425: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0
EXT4-fs error (device loop0): ext4_read_inline_dir:1593: inode #12: block 5: comm syz-executor425: path /0/file0/file0: bad entry in directory: rec_len % 4 != 0 - offset=24, inode=1633771873, rec_len=24929, size=148 fake=0
EXT4-fs error (device loop0): empty_inline_dir:1877: inode #12: block 5: comm syz-executor425: bad entry in directory: rec_len % 4 != 0 - offset=4, inode=1633771873, rec_len=24929, size=60 fake=0
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60
EXT4-fs warning (device loop0): empty_inline_dir:1884: bad inline directory (dir #12) - inode 1633771873, rec_len 24929, name_len 97inline size 60


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

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