linux-kernel - [syzbot] upstream boot error: kernel panic: corrupted stack end in call_usermodehelper_exec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <0000000000009aaff105e6b70769@google.com>
Date:   Sat, 20 Aug 2022 19:24:24 -0700
From:   syzbot <syzbot+af5fc6463cba536a92cb@...kaller.appspotmail.com>
To:     brauner@...nel.org, ebiederm@...ssion.com, keescook@...omium.org,
        linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: [syzbot] upstream boot error: kernel panic: corrupted stack end in call_usermodehelper_exec_async

Hello,

syzbot found the following issue on:

HEAD commit:    3cc40a443a04 Merge tag 'nios2_fixes_v6.0' of git://git.ker..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a080cb080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3b9175e0879a7749
dashboard link: https://syzkaller.appspot.com/bug?extid=af5fc6463cba536a92cb
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386

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

Kernel panic - not syncing: corrupted stack end detected inside scheduler
CPU: 0 PID: 1098 Comm: kworker/u4:4 Not tainted 6.0.0-rc1-syzkaller-00017-g3cc40a443a04 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 panic+0x2c8/0x627 kernel/panic.c:274
 schedule_debug kernel/sched/core.c:5737 [inline]
 __schedule+0x52a8/0x52b0 kernel/sched/core.c:6388
 do_task_dead+0xd1/0x100 kernel/sched/core.c:6512
 do_exit+0x18be/0x29b0 kernel/exit.c:847
 call_usermodehelper_exec_async+0x418/0x580 kernel/umh.c:125
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
general protection fault, maybe for address 0x80000002: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 1098 Comm: kworker/u4:4 Not tainted 6.0.0-rc1-syzkaller-00017-g3cc40a443a04 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
RIP: 0010:delay_tsc+0x9b/0xb0 arch/x86/lib/delay.c:97
Code: e8 54 d4 db fc eb b4 48 29 dd 49 01 ed eb 93 bf 01 00 00 00 e8 e6 19 2e fd 65 8b 05 af ce dd 7b 85 c0 74 07 5b 5d 41 5c 41 5d <c3> e8 29 d4 db fc 5b 5d 41 5c 41 5d c3 0f 1f 84 00 00 00 00 00 48
RSP: 0000:ffffc90004e8fbe8 EFLAGS: 00010082
RAX: 0000000080000002 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 0000000000000004 RSI: 0000000000000003 RDI: 0000000000000001
RBP: ffff000000000000 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000044 R11: 6e69746f6f626552 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000043 R15: 0000000000000043
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:delay_tsc+0x9b/0xb0 arch/x86/lib/delay.c:97
Code: e8 54 d4 db fc eb b4 48 29 dd 49 01 ed eb 93 bf 01 00 00 00 e8 e6 19 2e fd 65 8b 05 af ce dd 7b 85 c0 74 07 5b 5d 41 5c 41 5d <c3> e8 29 d4 db fc 5b 5d 41 5c 41 5d c3 0f 1f 84 00 00 00 00 00 48
RSP: 0000:ffffc90004e8fbe8 EFLAGS: 00010082
RAX: 0000000080000002 RBX: 0000000000000000 RCX: 0000000000000001
RDX: 0000000000000004 RSI: 0000000000000003 RDI: 0000000000000001
RBP: ffff000000000000 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000044 R11: 6e69746f6f626552 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000043 R15: 0000000000000043
FS:  0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff88823ffff000 CR3: 000000000bc8e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	e8 54 d4 db fc       	callq  0xfcdbd459
   5:	eb b4                	jmp    0xffffffbb
   7:	48 29 dd             	sub    %rbx,%rbp
   a:	49 01 ed             	add    %rbp,%r13
   d:	eb 93                	jmp    0xffffffa2
   f:	bf 01 00 00 00       	mov    $0x1,%edi
  14:	e8 e6 19 2e fd       	callq  0xfd2e19ff
  19:	65 8b 05 af ce dd 7b 	mov    %gs:0x7bddceaf(%rip),%eax        # 0x7bddcecf
  20:	85 c0                	test   %eax,%eax
  22:	74 07                	je     0x2b
  24:	5b                   	pop    %rbx
  25:	5d                   	pop    %rbp
  26:	41 5c                	pop    %r12
  28:	41 5d                	pop    %r13
* 2a:	c3                   	retq <-- trapping instruction
  2b:	e8 29 d4 db fc       	callq  0xfcdbd459
  30:	5b                   	pop    %rbx
  31:	5d                   	pop    %rbp
  32:	41 5c                	pop    %r12
  34:	41 5d                	pop    %r13
  36:	c3                   	retq
  37:	0f 1f 84 00 00 00 00 	nopl   0x0(%rax,%rax,1)
  3e:	00
  3f:	48                   	rex.W


---
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 syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.