[v5.15] WARNING in udf_free_inode (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 01879f56bdde Linux 5.15.190
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14f57a62580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4bfb7f3ca9a4e172
dashboard link: https://syzkaller.appspot.com/bug?extid=3fc6563fad3d5c2ae963
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/47310f1c8692/disk-01879f56.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d4d20855b227/vmlinux-01879f56.xz
kernel image: https://storage.googleapis.com/syzbot-assets/958809b6d16d/bzImage-01879f56.xz

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5823 at fs/udf/udfdecl.h:127 udf_updated_lvid fs/udf/udfdecl.h:125 [inline]
WARNING: CPU: 1 PID: 5823 at fs/udf/udfdecl.h:127 udf_free_inode+0x21c/0x2d0 fs/udf/ialloc.c:41
Modules linked in:
CPU: 1 PID: 5823 Comm: syz.2.313 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:udf_updated_lvid fs/udf/udfdecl.h:125 [inline]
RIP: 0010:udf_free_inode+0x21c/0x2d0 fs/udf/ialloc.c:41
Code: ff ff 4c 89 f7 31 f6 48 89 da 31 c9 41 b8 01 00 00 00 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d e9 e9 91 ff ff e8 04 b8 b5 fe <0f> 0b e9 74 ff ff ff 89 d9 80 e1 07 fe c1 38 c1 0f 8c 72 fe ff ff
RSP: 0018:ffffc90003e9fb10 EFLAGS: 00010287
RAX: ffffffff82c212ac RBX: ffff88806072b498 RCX: 0000000000080000
RDX: ffffc90011130000 RSI: 000000000000b426 RDI: 000000000000b427
RBP: 000000009d4b3a86 R08: dffffc0000000000 R09: fffff520007d3f1d
R10: fffff520007d3f1d R11: 1ffff920007d3f1c R12: 1ffff1100489f0cf
R13: ffff88806affd01c R14: dffffc0000000000 R15: ffff8880244f8678
FS: 00007f2dda3256c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5767b87000 CR3: 0000000064ea3000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
evict+0x485/0x870 fs/inode.c:647
__dentry_kill+0x431/0x650 fs/dcache.c:586
dentry_kill+0xb8/0x290 fs/dcache.c:-1
dput+0xd8/0x1a0 fs/dcache.c:893
do_renameat2+0x704/0xf70 fs/namei.c:4987
__do_sys_rename fs/namei.c:5031 [inline]
__se_sys_rename fs/namei.c:5029 [inline]
__x64_sys_rename+0x82/0x90 fs/namei.c:5029
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f2ddc0ffbe9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2dda325038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f2ddc337180 RCX: 00007f2ddc0ffbe9
RDX: 0000000000000000 RSI: 0000200000000040 RDI: 0000200000000000
RBP: 00007f2ddc182e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2ddc337218 R14: 00007f2ddc337180 R15: 00007ffcc6272538
</TASK>


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