Hello,
syzbot found the following issue on:
HEAD commit: 0d108e1e8c7b Merge 5.15.225 into android13-5.15-lts
git tree: android13-5.15-lts
console output:
https://syzkaller.appspot.com/x/log.txt?x=1474d34d580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=d4c6979904df126a
dashboard link:
https://syzkaller.appspot.com/bug?extid=60a10fdff9947ea556c8
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=15f51cd5580000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=1274d34d580000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/91be612629ca/disk-0d108e1e.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/740c5ceb0fdc/vmlinux-0d108e1e.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/9aff76d74f5a/bzImage-0d108e1e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+60a10f...@syzkaller.appspotmail.com
tipc: Enabling of bearer <eth:syz_tun> rejected, already enabled
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: 467 Comm: syz.2.87 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:203 [inline]
RIP: 0010:tipc_named_node_up+0xa21/0xc60 net/tipc/name_distr.c:229
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 00 cc 0f fd 48 8d b4 24 a0 00 00
RSP: 0018:ffffc90002c0f3c0 EFLAGS: 00010202
RAX: 000000000000001c RBX: 00000000000000e0 RCX: ffff8881151de400
RDX: 0000000000000000 RSI: ffffc90002c0f460 RDI: ffff88811dd2a010
RBP: ffffc90002c0f4f0 R08: ffff8881157e3807 R09: 1ffff11022afc700
R10: dffffc0000000000 R11: ffffed1022afc701 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000000456 R15: ffff88810ec59178
FS: 000055558fb32500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6c7aae73c0 CR3: 000000010f414000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
tipc_node_write_unlock+0x296/0x460 net/tipc/node.c:430
tipc_node_link_up+0x95/0xc0 net/tipc/node.c:936
tipc_rcv+0xaec/0xf70 net/tipc/node.c:2198
tipc_l2_rcv_msg+0x18c/0x200 net/tipc/bearer.c:658
__netif_receive_skb_one_core net/core/dev.c:5560 [inline]
__netif_receive_skb+0xc8/0x280 net/core/dev.c:5674
netif_receive_skb_internal net/core/dev.c:5760 [inline]
netif_receive_skb+0x98/0x3e0 net/core/dev.c:5819
tun_rx_batched+0x600/0x750 drivers/net/tun.c:-1
tun_get_user+0x2809/0x33e0 drivers/net/tun.c:2000
tun_chr_write_iter+0x1ed/0x2f0 drivers/net/tun.c:2030
call_write_iter include/linux/fs.h:2218 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x831/0xfd0 fs/read_write.c:594
ksys_write+0x14a/0x260 fs/read_write.c:647
__do_sys_write fs/read_write.c:659 [inline]
__se_sys_write fs/read_write.c:656 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:656
x64_sys_call+0x8ef/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:2
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:0x7f70f86c76d7
Code: 48 89 fa 4c 89 df e8 a8 56 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:00007ffce6c1fc60 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000055558fb32500 RCX: 00007f70f86c76d7
RDX: 0000000000000046 RSI: 0000200000000140 RDI: 00000000000000c8
RBP: 00007f70f879b136 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000000
R13: 00007f70f8988fac R14: 00007f70f8988fa0 R15: 00007f70f8988fa0
</TASK>
Modules linked in:
---[ end trace a5b457a42a8a63f2 ]---
RIP: 0010:buf_msg net/tipc/msg.h:202 [inline]
RIP: 0010:named_distribute net/tipc/name_distr.c:203 [inline]
RIP: 0010:tipc_named_node_up+0xa21/0xc60 net/tipc/name_distr.c:229
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 00 cc 0f fd 48 8d b4 24 a0 00 00
RSP: 0018:ffffc90002c0f3c0 EFLAGS: 00010202
RAX: 000000000000001c RBX: 00000000000000e0 RCX: ffff8881151de400
RDX: 0000000000000000 RSI: ffffc90002c0f460 RDI: ffff88811dd2a010
RBP: ffffc90002c0f4f0 R08: ffff8881157e3807 R09: 1ffff11022afc700
R10: dffffc0000000000 R11: ffffed1022afc701 R12: dffffc0000000000
R13: 0000000000000000 R14: 0000000000000456 R15: ffff88810ec59178
FS: 000055558fb32500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6c7aae73c0 CR3: 000000010f414000 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 00 cc 0f fd call 0xfd0fcc39
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 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