[Android 5.10] general protection fault in cleanup_bearer

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4055d754db6f ANDROID: fix up crc problems 5.10.231
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=12dbc2c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=705d8836f7783529
dashboard link: https://syzkaller.appspot.com/bug?extid=b793153f7d0028dac753
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d9e0b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16dbc2c4580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2123b0b97b49/disk-4055d754.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ffaa94327673/vmlinux-4055d754.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6199bf227af4/bzImage-4055d754.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9593ad194412/mount_0.gz

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

general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]
CPU: 1 PID: 25 Comm: kworker/1:1 Not tainted 5.10.231-syzkaller-00700-g4055d754db6f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events cleanup_bearer
RIP: 0010:read_pnet include/net/net_namespace.h:335 [inline]
RIP: 0010:sock_net include/net/sock.h:2653 [inline]
RIP: 0010:cleanup_bearer+0x1dc/0x2b0 net/tipc/udp_media.c:815
Code: 8b 1e 48 83 c3 18 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 42 16 0a fd 48 8b 1b 48 83 c3 30 48 89 d8 48 c1 e8 03 <42> 80 3c 28 00 74 08 48 89 df e8 25 16 0a fd 4c 8b 33 48 c7 c0 80
RSP: 0018:ffffc900001afcf0 EFLAGS: 00010206
RAX: 0000000000000006 RBX: 0000000000000030 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff867996f0
RBP: ffffc900001afd30 R08: dffffc0000000000 R09: fffffbfff0cf32df
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888109acfe00
R13: dffffc0000000000 R14: ffff88810f10ac08 R15: ffff88810f10ac18
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f600f460ae0 CR3: 000000000660f000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
process_one_work+0x6dc/0xbd0 kernel/workqueue.c:2301
worker_thread+0xaea/0x1510 kernel/workqueue.c:2447
kthread+0x34b/0x3d0 kernel/kthread.c:313
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
Modules linked in:
---[ end trace be534e2e2457556a ]---
RIP: 0010:read_pnet include/net/net_namespace.h:335 [inline]
RIP: 0010:sock_net include/net/sock.h:2653 [inline]
RIP: 0010:cleanup_bearer+0x1dc/0x2b0 net/tipc/udp_media.c:815
Code: 8b 1e 48 83 c3 18 48 89 d8 48 c1 e8 03 42 80 3c 28 00 74 08 48 89 df e8 42 16 0a fd 48 8b 1b 48 83 c3 30 48 89 d8 48 c1 e8
----------------
Code disassembly (best guess):
0: 8b 1e mov (%rsi),%ebx
2: 48 83 c3 18 add $0x18,%rbx
6: 48 89 d8 mov %rbx,%rax
9: 48 c1 e8 03 shr $0x3,%rax
d: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1)
12: 74 08 je 0x1c
14: 48 89 df mov %rbx,%rdi
17: e8 42 16 0a fd call 0xfd0a165e
1c: 48 8b 1b mov (%rbx),%rbx
1f: 48 83 c3 30 add $0x30,%rbx
23: 48 89 d8 mov %rbx,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 80 3c 28 00 cmpb $0x0,(%rax,%r13,1) <-- trapping instruction
2f: 74 08 je 0x39
31: 48 89 df mov %rbx,%rdi
34: e8 25 16 0a fd call 0xfd0a165e
39: 4c 8b 33 mov (%rbx),%r14
3c: 48 rex.W
3d: c7 .byte 0xc7
3e: c0 .byte 0xc0
3f: 80 .byte 0x80


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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.