[Android 5.10] general protection fault in tipc_named_node_up

1 view
Skip to first unread message

syzbot

unread,
Nov 9, 2026, 4:09:29 AM (11 days ago) Nov 9
to syzkaller-a...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: f61a392235e0 Merge 5.10.272 into android13-5.10-lts
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=15c99f8d580000
kernel config: https://syzkaller.appspot.com/x/.config?x=40fa24cc6888ca30
dashboard link: https://syzkaller.appspot.com/bug?extid=7d57d478323ec5489781
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16c17f8d580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13c99f8d580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1067764b73c1/disk-f61a3922.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eda1b07ee362/vmlinux-f61a3922.xz
kernel image: https://storage.googleapis.com/syzbot-assets/109d1701bea2/bzImage-f61a3922.xz

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

general protection fault, probably for non-canonical address 0xdffffc000000001c: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x00000000000000e0-0x00000000000000e7]
CPU: 1 PID: 383 Comm: syz-executor398 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/06/2026
RIP: 0010:buf_msg net/tipc/msg.h:202 [inline]
RIP: 0010:named_distribute net/tipc/name_distr.c:190 [inline]
RIP: 0010:tipc_named_node_up+0xa21/0xc60 net/tipc/name_distr.c:213
Code: b4 24 a0 00 00 00 44 8b 6c 24 2c 48 8b 84 24 a8 00 00 00 31 db 48 39 f0 48 0f 45 d8 48 81 c3 e0 00 00 00 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 10 48 89 df e8 40 e3 3a fd 48 8d b4 24 a0 00 00
RSP: 0018:ffffc90000d374a0 EFLAGS: 00010202
RAX: 000000000000001c RBX: 00000000000000e0 RCX: ffff88810cece400
RDX: 0000000000000000 RSI: ffffc90000d37540 RDI: ffff8881205d6010
RBP: ffffc90000d375d0 R08: ffff88810e9e1807 R09: 1ffff11021d3c300
R10: dffffc0000000000 R11: ffffed1021d3c301 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000000456 R15: ffff888120545178
FS: 0000555561d5e3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000010ab29000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
tipc_node_write_unlock+0x1a0/0x310 net/tipc/node.c:412
tipc_node_link_up+0x95/0xc0 net/tipc/node.c:914
tipc_rcv+0xa55/0xea0 net/tipc/node.c:2165
tipc_l2_rcv_msg+0x18c/0x200 net/tipc/bearer.c:642
__netif_receive_skb_one_core net/core/dev.c:5414 [inline]
__netif_receive_skb+0xc8/0x280 net/core/dev.c:5528
netif_receive_skb_internal net/core/dev.c:5633 [inline]
netif_receive_skb+0x9b/0x3e0 net/core/dev.c:5692
tun_rx_batched+0x600/0x750 drivers/net/tun.c:-1
tun_get_user+0x26f6/0x31a0 drivers/net/tun.c:2037
tun_chr_write_iter+0x1c1/0x270 drivers/net/tun.c:2070
call_write_iter include/linux/fs.h:2072 [inline]
new_sync_write fs/read_write.c:518 [inline]
vfs_write+0x770/0xd70 fs/read_write.c:605
ksys_write+0x14a/0x260 fs/read_write.c:658
__do_sys_write fs/read_write.c:670 [inline]
__se_sys_write fs/read_write.c:667 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:667
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f711077c427
Code: 48 89 fa 4c 89 df e8 78 1e 00 00 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 1a 5b c3 0f 1f 84 00 00 00 00 00 48 8b 44 24 10 0f 05 <5b> c3 0f 1f 80 00 00 00 00 83 e2 39 83 fa 08 75 de e8 23 ff ff ff
RSP: 002b:00007ffc96534670 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000555561d5e3c0 RCX: 00007f711077c427
RDX: 0000000000000046 RSI: 0000200000000140 RDI: 00000000000000c8
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 00007ffc965346dc
R13: 00007ffc96534710 R14: 00007ffc965346f0 R15: 000000000000000f
Modules linked in:
---[ end trace 373717d0d694e6fd ]---
RIP: 0010:buf_msg net/tipc/msg.h:202 [inline]
RIP: 0010:named_distribute net/tipc/name_distr.c:190 [inline]
RIP: 0010:tipc_named_node_up+0xa21/0xc60 net/tipc/name_distr.c:213
Code: b4 24 a0 00 00 00 44 8b 6c 24 2c 48 8b 84 24 a8 00 00 00 31 db 48 39 f0 48 0f 45 d8 48 81 c3 e0 00 00 00 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 10 48 89 df e8 40 e3 3a fd 48 8d b4 24 a0 00 00
RSP: 0018:ffffc90000d374a0 EFLAGS: 00010202

RAX: 000000000000001c RBX: 00000000000000e0 RCX: ffff88810cece400
RDX: 0000000000000000 RSI: ffffc90000d37540 RDI: ffff8881205d6010
RBP: ffffc90000d375d0 R08: ffff88810e9e1807 R09: 1ffff11021d3c300
R10: dffffc0000000000 R11: ffffed1021d3c301 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000000456 R15: ffff888120545178
FS: 0000555561d5e3c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000010ab29000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: b4 24 mov $0x24,%ah
2: a0 00 00 00 44 8b 6c movabs 0x2c246c8b44000000,%al
9: 24 2c
b: 48 8b 84 24 a8 00 00 mov 0xa8(%rsp),%rax
12: 00
13: 31 db xor %ebx,%ebx
15: 48 39 f0 cmp %rsi,%rax
18: 48 0f 45 d8 cmovne %rax,%rbx
1c: 48 81 c3 e0 00 00 00 add $0xe0,%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 20 00 cmpb $0x0,(%rax,%r12,1) <-- trapping instruction
2f: 74 10 je 0x41
31: 48 89 df mov %rbx,%rdi
34: e8 40 e3 3a fd call 0xfd3ae379
39: 48 rex.W
3a: 8d .byte 0x8d
3b: b4 24 mov $0x24,%ah
3d: a0 .byte 0xa0


---
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
Reply all
Reply to author
Forward
0 new messages