Hello,
syzbot found the following issue on:
HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=10183cc2580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link:
https://syzkaller.appspot.com/bug?extid=c0e2e58f45917625155b
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/c71c660545b2/disk-cc5ec876.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/4f011826cca6/vmlinux-cc5ec876.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/8ccd1a2c3f8c/bzImage-cc5ec876.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+c0e2e5...@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5097 at net/ipv4/af_inet.c:157 inet_sock_destruct+0x63b/0x730 net/ipv4/af_inet.c:157
Modules linked in:
CPU: 0 PID: 5097 Comm: syz.1.254 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:inet_sock_destruct+0x63b/0x730 net/ipv4/af_inet.c:157
Code: 01 e8 c9 f3 10 f9 0f 0b e9 64 fe ff ff e8 bd f3 10 f9 0f 0b e9 99 fe ff ff e8 b1 f3 10 f9 0f 0b e9 c1 fe ff ff e8 a5 f3 10 f9 <0f> 0b e9 e9 fe ff ff 44 89 f1 80 e1 07 fe c1 38 c1 0f 8c 5b fd ff
RSP: 0018:ffffc90000007b20 EFLAGS: 00010246
RAX: ffffffff8866d86b RBX: dffffc0000000000 RCX: ffff88807db0bb80
RDX: 0000000000000100 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000080000000 R08: dffffc0000000000 R09: ffffed1029910830
R10: ffffed1029910830 R11: 1ffff1102991082f R12: ffff88814c883f00
R13: ffff88814c883f00 R14: ffff88814c884120 R15: 1ffff110299107e2
FS: 00007f393686c6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c299ed7 CR3: 000000006514c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
__sk_destruct+0x50/0x840 net/core/sock.c:1961
sock_put include/net/sock.h:1976 [inline]
sctp_endpoint_destroy_rcu+0x9d/0xe0 net/sctp/endpointola.c:193
rcu_do_batch kernel/rcu/tree.c:2523 [inline]
rcu_core+0x962/0x15d0 kernel/rcu/tree.c:2763
handle_softirqs+0x328/0x820 kernel/softirq.c:576
__do_softirq kernel/softirq.c:610 [inline]
invoke_softirq kernel/softirq.c:450 [inline]
__irq_exit_rcu+0x12f/0x220 kernel/softirq.c:659
irq_exit_rcu+0x5/0x20 kernel/softirq.c:671
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1108 [inline]
sysvec_apic_timer_interrupt+0xa0/0xc0 arch/x86/kernel/apic/apic.c:1108
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:676
RIP: 0010:kasan_mem_to_shadow include/linux/kasan.h:55 [inline]
RIP: 0010:memory_is_poisoned_n mm/kasan/generic.c:129 [inline]
RIP: 0010:memory_is_poisoned mm/kasan/generic.c:159 [inline]
RIP: 0010:check_region_inline mm/kasan/generic.c:180 [inline]
RIP: 0010:kasan_check_range+0x54/0x290 mm/kasan/generic.c:189
Code: 0f 82 43 02 00 00 49 bf 01 00 00 00 00 fc ff df 49 89 fb 49 c1 eb 03 49 b8 00 00 00 00 00 fc ff df 4f 8d 0c 03 48 8d 5c 37 ff <48> c1 eb 03 4e 8d 14 3b 4d 89 d6 4d 29 ce 49 83 fe 10 7f 26 4d 85
RSP: 0018:ffffc90003227ca0 EFLAGS: 00000a02
RAX: 1ffff92000644f01 RBX: ffff88807db0bb87 RCX: ffffffff812952d5
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffff88807db0bb80
RBP: ffffc90003227ec0 R08: dffffc0000000000 R09: ffffed100fb61770
R10: ffffed1004996a69 R11: 1ffff1100fb61770 R12: ffffc90003227de0
R13: 0000000000000000 R14: ffffc90003227fd0 R15: dffffc0000000001
instrument_atomic_read include/linux/instrumented.h:71 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
test_ti_thread_flag include/linux/thread_info.h:118 [inline]
handle_signal arch/x86/kernel/signal.c:820 [inline]
arch_do_signal_or_restart+0x185/0x1300 arch/x86/kernel/signal.c:869
handle_signal_work kernel/entry/common.c:154 [inline]
exit_to_user_mode_loop+0x9e/0x130 kernel/entry/common.c:178
exit_to_user_mode_prepare+0xee/0x180 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:307
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f3938605749
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:00007f393686c038 EFLAGS: 00000246
RAX: ffffffffffffffea RBX: 00007f393885bfa0 RCX: 00007f3938605749
RDX: 0000000000000000 RSI: 0000200000001100 RDI: ffffffffffffffff
RBP: 00007f3938689f91 R08: 0000000000000800 R09: 0000000000000000
R10: 0000200000000240 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f393885c038 R14: 00007f393885bfa0 R15: 00007ffe691ecd18
</TASK>
----------------
Code disassembly (best guess):
0: 0f 82 43 02 00 00 jb 0x249
6: 49 bf 01 00 00 00 00 movabs $0xdffffc0000000001,%r15
d: fc ff df
10: 49 89 fb mov %rdi,%r11
13: 49 c1 eb 03 shr $0x3,%r11
17: 49 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%r8
1e: fc ff df
21: 4f 8d 0c 03 lea (%r11,%r8,1),%r9
25: 48 8d 5c 37 ff lea -0x1(%rdi,%rsi,1),%rbx
* 2a: 48 c1 eb 03 shr $0x3,%rbx <-- trapping instruction
2e: 4e 8d 14 3b lea (%rbx,%r15,1),%r10
32: 4d 89 d6 mov %r10,%r14
35: 4d 29 ce sub %r9,%r14
38: 49 83 fe 10 cmp $0x10,%r14
3c: 7f 26 jg 0x64
3e: 4d rex.WRB
3f: 85 .byte 0x85
---
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