[Android 5.15] kernel BUG in binder_inc_ref_for_node

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2d18a4de3623 Merge android13-5.15 into android13-5.15-lts
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=150ae415580000
kernel config: https://syzkaller.appspot.com/x/.config?x=43676e801f1929a9
dashboard link: https://syzkaller.appspot.com/bug?extid=4c25498cf4f5436c1c39
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1190719e580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17247179580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fb52db041f8c/disk-2d18a4de.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ff66016e9406/vmlinux-2d18a4de.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b418483ef9b1/bzImage-2d18a4de.xz

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

------------[ cut here ]------------
kernel BUG at drivers/android/binder.c:1330!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 305 Comm: syz-executor127 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:binder_get_ref_for_node_olocked drivers/android/binder.c:1330 [inline]
RIP: 0010:binder_inc_ref_for_node+0x10b3/0x11c0 drivers/android/binder.c:1642
Code: ff ff 48 89 df 41 89 f5 41 89 d7 41 89 ce e8 84 04 11 fe 44 89 f1 4c 8b 75 c8 44 89 fa 44 89 ee e9 a3 fe ff ff e8 1d 95 d1 fd <0f> 0b 65 8b 05 ac ee 69 7c 41 89 c5 c1 e8 06 48 8d 3c c5 a8 51 e9
RSP: 0018:ffffc900009a7370 EFLAGS: 00010293
RAX: ffffffff83982293 RBX: 0000000000000000 RCX: ffff888124508000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900009a7410 R08: ffff888107ddee3f R09: ffff888107ddee30
R10: dffffc0000000000 R11: ffffed1020fbbdc8 R12: dffffc0000000000
R13: ffff888107ddef28 R14: ffff888107ddef10 R15: 0000000000000000
FS: 000055556d6383c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000062b5d8 CR3: 0000000122746000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
binder_thread_write+0x1497/0x6fe0 drivers/android/binder.c:4239
binder_ioctl_write_read+0x203/0x6700 drivers/android/binder.c:5579
binder_ioctl+0x36c/0x1df0 drivers/android/binder.c:5905
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:874 [inline]
__se_sys_ioctl+0x121/0x1a0 fs/ioctl.c:860
__x64_sys_ioctl+0x7b/0x90 fs/ioctl.c:860
x64_sys_call+0x2f/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:17
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:0x7fbb6a4c3e09
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 0f 1f 44 00 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 d8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffda234bc58 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007fbb6a4c3e09
RDX: 00002000000003c0 RSI: 00000000c0306201 RDI: 0000000000000003
RBP: 00000000000f4240 R08: 000055556d639670 R09: 000055556d639670
R10: 000055556d639670 R11: 0000000000000246 R12: 00007fbb6a52de0e
R13: 00007fbb6a52c0a7 R14: 00007ffda234bc70 R15: 00007ffda234bc80
</TASK>
Modules linked in:
---[ end trace c210fb6709c0be6b ]---
RIP: 0010:binder_get_ref_for_node_olocked drivers/android/binder.c:1330 [inline]
RIP: 0010:binder_inc_ref_for_node+0x10b3/0x11c0 drivers/android/binder.c:1642
Code: ff ff 48 89 df 41 89 f5 41 89 d7 41 89 ce e8 84 04 11 fe 44 89 f1 4c 8b 75 c8 44 89 fa 44 89 ee e9 a3 fe ff ff e8 1d 95 d1 fd <0f> 0b 65 8b 05 ac ee 69 7c 41 89 c5 c1 e8 06 48 8d 3c c5 a8 51 e9
RSP: 0018:ffffc900009a7370 EFLAGS: 00010293
RAX: ffffffff83982293 RBX: 0000000000000000 RCX: ffff888124508000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900009a7410 R08: ffff888107ddee3f R09: ffff888107ddee30
R10: dffffc0000000000 R11: ffffed1020fbbdc8 R12: dffffc0000000000
R13: ffff888107ddef28 R14: ffff888107ddef10 R15: 0000000000000000
FS: 000055556d6383c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000062b5d8 CR3: 0000000122746000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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