[Android 5.15] UBSAN: shift-out-of-bounds in ext4_fill_super

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 28e3f5851a99 Revert "HID: core: store the unique system id..
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=129cfc81e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=77b14bc9a56d2541
dashboard link: https://syzkaller.appspot.com/bug?extid=f358aa23cf81d2593253
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=14912f76e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114611cee80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ae34678aaf41/disk-28e3f585.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ce3daedc6cc4/vmlinux-28e3f585.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ced16d9f3bc0/bzImage-28e3f585.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/4bd1dfaa330f/mount_0.gz

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

loop5: detected capacity change from 0 to 512
================================================================================
UBSAN: shift-out-of-bounds in fs/ext4/super.c:4423:27
shift exponent 59 is too large for 32-bit type 'int'
CPU: 0 PID: 572 Comm: syz-executor170 Not tainted 5.15.141-syzkaller-00899-g28e3f5851a99 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_shift_out_of_bounds+0x3bf/0x420 lib/ubsan.c:321
ext4_fill_super+0x7491/0x96e0 fs/ext4/super.c:4423
mount_bdev+0x282/0x3b0 fs/super.c:1387
ext4_mount+0x34/0x40 fs/ext4/super.c:6581
legacy_get_tree+0xf1/0x190 fs/fs_context.c:611
vfs_get_tree+0x88/0x290 fs/super.c:1517
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
path_mount+0x671/0x1070 fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3522
__x64_sys_mount+0xbf/0xd0 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:0x7f0c4a25309a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 5e 04 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 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:00007f0c4a20e088 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f0c4a25309a
RDX: 0000000020000040 RSI: 0000000020000080 RDI: 00007f0c4a20e0a0
RBP: 00007f0c4a20e0a0 R08: 00007f0c4a20e0e0 R09: 00000000000004d6
R10: 0000000000004500 R11: 0000000000000202 R12: 00007f0c4a20e0e0
R13: 0000000000004500 R14: 0000000000000003 R15: 0000000000040000
</TASK>
================================================================================
EXT4-fs (loop5): fragment/cluster size (0) != block size (4096)


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