[syzbot] [fs?] kernel BUG in socket

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 92fd6e84175b Add linux-next specific files for 20251125
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17d79612580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c8705ffbbff9235f
dashboard link: https://syzkaller.appspot.com/bug?extid=e956b5830b1895c9cb7b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16a3c57c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130acf42580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/504ec57bbfb4/disk-92fd6e84.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90731c1057eb/vmlinux-92fd6e84.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7066fa5b18b8/bzImage-92fd6e84.xz

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

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007fa38bbe5fa0 R14: 00007fa38bbe5fa0 R15: 0000000000000000
</TASK>
VFS_BUG_ON_INODE(inode_state_read_once(inode) & I_CLEAR) encountered for inode ffff88805b5d5140
fs sockfs mode 140777 opflags 0x8 flags 0x0 state 0x300 count 0
------------[ cut here ]------------
kernel BUG at fs/inode.c:1978!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 6012 Comm: syz.0.18 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:iput+0xfc9/0x1030 fs/inode.c:1978
Code: 8b 7c 24 18 48 c7 c6 80 c0 99 8b e8 61 c1 e6 fe 90 0f 0b e8 19 7b 80 ff 48 8b 7c 24 18 48 c7 c6 20 c0 99 8b e8 48 c1 e6 fe 90 <0f> 0b 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c cd fb ff ff 4c 89 ef
RSP: 0018:ffffc90002ff7de0 EFLAGS: 00010282
RAX: 000000000000009f RBX: dffffc0000000000 RCX: 9e18d727a1916b00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffffffff1f54606 R08: ffffc90002ff7aa7 R09: 1ffff920005fef54
R10: dffffc0000000000 R11: fffff520005fef55 R12: 1ffff1100b6baa68
R13: ffff88805b5d5340 R14: 0000000000000200 R15: 1ffffffff1f7f5d4
FS: 000055556e081500(0000) GS:ffff888125b41000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ec8d3e1138 CR3: 0000000076182000 CR4: 00000000003526f0
Call Trace:
<TASK>
sock_release net/socket.c:685 [inline]
sock_map_fd net/socket.c:510 [inline]
__sys_socket+0x2f0/0x370 net/socket.c:1762
__do_sys_socket net/socket.c:1767 [inline]
__se_sys_socket net/socket.c:1765 [inline]
__x64_sys_socket+0x7a/0x90 net/socket.c:1765
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fa38b98f749
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:00007ffe62833658 EFLAGS: 00000246 ORIG_RAX: 0000000000000029
RAX: ffffffffffffffda RBX: 00007fa38bbe5fa0 RCX: 00007fa38b98f749
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: 0000000000000004 R08: 0000000000000000 R09: 00000000000927c0
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000002
R13: 00007fa38bbe5fa0 R14: 00007fa38bbe5fa0 R15: 0000000000000000
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:iput+0xfc9/0x1030 fs/inode.c:1978
Code: 8b 7c 24 18 48 c7 c6 80 c0 99 8b e8 61 c1 e6 fe 90 0f 0b e8 19 7b 80 ff 48 8b 7c 24 18 48 c7 c6 20 c0 99 8b e8 48 c1 e6 fe 90 <0f> 0b 44 89 e9 80 e1 07 80 c1 03 38 c1 0f 8c cd fb ff ff 4c 89 ef
RSP: 0018:ffffc90002ff7de0 EFLAGS: 00010282
RAX: 000000000000009f RBX: dffffc0000000000 RCX: 9e18d727a1916b00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffffffff1f54606 R08: ffffc90002ff7aa7 R09: 1ffff920005fef54
R10: dffffc0000000000 R11: fffff520005fef55 R12: 1ffff1100b6baa68
R13: ffff88805b5d5340 R14: 0000000000000200 R15: 1ffffffff1f7f5d4
FS: 000055556e081500(0000) GS:ffff888125b41000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ec8d3e1138 CR3: 0000000076182000 CR4: 00000000003526f0


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