[moderation] [sctp?] general protection fault in proc_sctp_do_udp_port
7 views
Skip to first unread message
syzbot
Jan 5, 2025, 10:12:26 AM1/5/25
to syzkaller-upst...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=152806c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=86dd15278dbfe19f
dashboard link: https://syzkaller.appspot.com/bug?extid=b46ce7dc4715558a6ac7
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [da...@davemloft.net edum...@google.com ho...@kernel.org ku...@kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org lucie...@gmail.com marcelo...@gmail.com net...@vger.kernel.org pab...@redhat.com]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d24eb225cff7/disk-ccb98cce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd81532f8240/vmlinux-ccb98cce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18b08e4bbf40/bzImage-ccb98cce.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b46ce7...@syzkaller.appspotmail.com
Process accounting resumed
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
CPU: 1 UID: 0 PID: 15494 Comm: syz.1.2092 Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:proc_sctp_do_udp_port+0xcd/0x4a0 net/sctp/sysctl.c:530
Code: 03 42 80 3c 30 00 0f 85 b6 03 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 84 03 00 00 49 8d 7d 28 4d 8b 64 24 28 48 b8 00
RSP: 0018:ffffc9000499f508 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 1ffff92000933ea4 RCX: ffffc9000499f650
RDX: 0000000000000005 RSI: ffffffff8a680795 RDI: 0000000000000028
RBP: 0000000000000001 R08: ffffc9000499f740 R09: 0000000000000040
R10: 0000000000000040 R11: 0000000000003239 R12: 0000000000000000
R13: ffff8880618fd5e8 R14: dffffc0000000000 R15: ffffc9000499f740
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000497000 CR3: 000000007ce84000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
proc_sys_call_handler+0x403/0x5d0 fs/proc/proc_sysctl.c:601
__kernel_write_iter+0x318/0xa80 fs/read_write.c:612
__kernel_write+0xf6/0x140 fs/read_write.c:632
do_acct_process+0xcb0/0x14a0 kernel/acct.c:539
acct_pin_kill+0x2d/0x100 kernel/acct.c:192
pin_kill+0x194/0x7c0 fs/fs_pin.c:44
mnt_pin_kill+0x61/0x1e0 fs/fs_pin.c:81
cleanup_mnt+0x3ac/0x450 fs/namespace.c:1366
task_work_run+0x14e/0x250 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0xad8/0x2d70 kernel/exit.c:938
do_group_exit+0xd3/0x2a0 kernel/exit.c:1087
get_signal+0x2576/0x2610 kernel/signal.c:3017
arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
irqentry_exit_to_user_mode+0x13f/0x280 kernel/entry/common.c:231
asm_exc_invalid_op+0x1a/0x20 arch/x86/include/asm/idtentry.h:621
RIP: 0033:0x458
Code: Unable to access opcode bytes at 0x42e.
RSP: 002b:0000000000000adb EFLAGS: 00010206
RAX: 0000000000000000 RBX: 00007f80b5776080 RCX: 00007f80b5585d29
RDX: 0000000000000000 RSI: 0000000000000ad3 RDI: 0000000000003fff
RBP: 00007f80b5601b08 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f80b5776080 R15: 00007ffcfe186fd8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:proc_sctp_do_udp_port+0xcd/0x4a0 net/sctp/sysctl.c:530
Code: 03 42 80 3c 30 00 0f 85 b6 03 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 84 03 00 00 49 8d 7d 28 4d 8b 64 24 28 48 b8 00
RSP: 0018:ffffc9000499f508 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 1ffff92000933ea4 RCX: ffffc9000499f650
RDX: 0000000000000005 RSI: ffffffff8a680795 RDI: 0000000000000028
RBP: 0000000000000001 R08: ffffc9000499f740 R09: 0000000000000040
R10: 0000000000000040 R11: 0000000000003239 R12: 0000000000000000
R13: ffff8880618fd5e8 R14: dffffc0000000000 R15: ffffc9000499f740
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000005a9000 CR3: 00000000508a0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 03 42 80 add -0x80(%rdx),%eax
3: 3c 30 cmp $0x30,%al
5: 00 0f add %cl,(%rdi)
7: 85 b6 03 00 00 4d test %esi,0x4d000003(%rsi)
d: 8b a4 24 08 09 00 00 mov 0x908(%rsp),%esp
14: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1b: fc ff df
1e: 49 8d 7c 24 28 lea 0x28(%r12),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 84 03 00 00 jne 0x3b8
34: 49 8d 7d 28 lea 0x28(%r13),%rdi
38: 4d 8b 64 24 28 mov 0x28(%r12),%r12
3d: 48 rex.W
3e: b8 .byte 0xb8
---
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
syzbot found the following issue on:
HEAD commit: ccb98ccef0e5 Merge tag 'platform-drivers-x86-v6.13-4' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=152806c4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=86dd15278dbfe19f
dashboard link: https://syzkaller.appspot.com/bug?extid=b46ce7dc4715558a6ac7
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [da...@davemloft.net edum...@google.com ho...@kernel.org ku...@kernel.org linux-...@vger.kernel.org linux...@vger.kernel.org lucie...@gmail.com marcelo...@gmail.com net...@vger.kernel.org pab...@redhat.com]
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d24eb225cff7/disk-ccb98cce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dd81532f8240/vmlinux-ccb98cce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18b08e4bbf40/bzImage-ccb98cce.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b46ce7...@syzkaller.appspotmail.com
Process accounting resumed
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
CPU: 1 UID: 0 PID: 15494 Comm: syz.1.2092 Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:proc_sctp_do_udp_port+0xcd/0x4a0 net/sctp/sysctl.c:530
Code: 03 42 80 3c 30 00 0f 85 b6 03 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 84 03 00 00 49 8d 7d 28 4d 8b 64 24 28 48 b8 00
RSP: 0018:ffffc9000499f508 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 1ffff92000933ea4 RCX: ffffc9000499f650
RDX: 0000000000000005 RSI: ffffffff8a680795 RDI: 0000000000000028
RBP: 0000000000000001 R08: ffffc9000499f740 R09: 0000000000000040
R10: 0000000000000040 R11: 0000000000003239 R12: 0000000000000000
R13: ffff8880618fd5e8 R14: dffffc0000000000 R15: ffffc9000499f740
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000497000 CR3: 000000007ce84000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
proc_sys_call_handler+0x403/0x5d0 fs/proc/proc_sysctl.c:601
__kernel_write_iter+0x318/0xa80 fs/read_write.c:612
__kernel_write+0xf6/0x140 fs/read_write.c:632
do_acct_process+0xcb0/0x14a0 kernel/acct.c:539
acct_pin_kill+0x2d/0x100 kernel/acct.c:192
pin_kill+0x194/0x7c0 fs/fs_pin.c:44
mnt_pin_kill+0x61/0x1e0 fs/fs_pin.c:81
cleanup_mnt+0x3ac/0x450 fs/namespace.c:1366
task_work_run+0x14e/0x250 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0xad8/0x2d70 kernel/exit.c:938
do_group_exit+0xd3/0x2a0 kernel/exit.c:1087
get_signal+0x2576/0x2610 kernel/signal.c:3017
arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
irqentry_exit_to_user_mode+0x13f/0x280 kernel/entry/common.c:231
asm_exc_invalid_op+0x1a/0x20 arch/x86/include/asm/idtentry.h:621
RIP: 0033:0x458
Code: Unable to access opcode bytes at 0x42e.
RSP: 002b:0000000000000adb EFLAGS: 00010206
RAX: 0000000000000000 RBX: 00007f80b5776080 RCX: 00007f80b5585d29
RDX: 0000000000000000 RSI: 0000000000000ad3 RDI: 0000000000003fff
RBP: 00007f80b5601b08 R08: 0000000000000002 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f80b5776080 R15: 00007ffcfe186fd8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:proc_sctp_do_udp_port+0xcd/0x4a0 net/sctp/sysctl.c:530
Code: 03 42 80 3c 30 00 0f 85 b6 03 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 84 03 00 00 49 8d 7d 28 4d 8b 64 24 28 48 b8 00
RSP: 0018:ffffc9000499f508 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 1ffff92000933ea4 RCX: ffffc9000499f650
RDX: 0000000000000005 RSI: ffffffff8a680795 RDI: 0000000000000028
RBP: 0000000000000001 R08: ffffc9000499f740 R09: 0000000000000040
R10: 0000000000000040 R11: 0000000000003239 R12: 0000000000000000
R13: ffff8880618fd5e8 R14: dffffc0000000000 R15: ffffc9000499f740
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000005a9000 CR3: 00000000508a0000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: 03 42 80 add -0x80(%rdx),%eax
3: 3c 30 cmp $0x30,%al
5: 00 0f add %cl,(%rdi)
7: 85 b6 03 00 00 4d test %esi,0x4d000003(%rsi)
d: 8b a4 24 08 09 00 00 mov 0x908(%rsp),%esp
14: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
1b: fc ff df
1e: 49 8d 7c 24 28 lea 0x28(%r12),%rdi
23: 48 89 fa mov %rdi,%rdx
26: 48 c1 ea 03 shr $0x3,%rdx
* 2a: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2e: 0f 85 84 03 00 00 jne 0x3b8
34: 49 8d 7d 28 lea 0x28(%r13),%rdi
38: 4d 8b 64 24 28 mov 0x28(%r12),%r12
3d: 48 rex.W
3e: b8 .byte 0xb8
---
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
syzbot
Apr 1, 2025, 11:06:24 AM4/1/25
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages