syzbot

 sign-in | mailing list | source | docs
🐞 Open [1596]
≡ Subsystems
🐞 Fixed [6224]
🐞 Invalid [15742]
⬇ Missing Backports [183]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
Total Repo Heatmap Subsystems Heatmap
💬 Send us feedback

BUG: scheduling while atomic in __stack_chk_fail

Status: closed as invalid on 2024/09/13 10:29
Subsystems: kernel
[Documentation on labels]
First crash: 264d, last: 262d
▶ ▼ Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream KASAN: stack-out-of-bounds Write in __stack_chk_fail kernel 3 263d 264d 0/28 closed as invalid on 2024/09/13 10:29

Sample crash report:
BUG: scheduling while atomic: syz.3.139/5973/0x00000003
BUG: kernel NULL pointer dereference, address: 0000000000000018
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 8000000063769067 P4D 8000000063769067 PUD 68216067 PMD 0 
Oops: Oops: 0010 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 5973 Comm: syz.3.139 Not tainted 6.11.0-rc4-next-20240822-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:0x18
Code: Unable to access opcode bytes at 0xffffffffffffffee.
RSP: 0018:ffffc9000308eba0 EFLAGS: 00010002
RAX: ffffffff93195b80 RBX: 000000000000002f RCX: ffffffff8bb86308
RDX: 000000000000000f RSI: ffffffff8c0995e0 RDI: ffffffff93195ba0
RBP: ffffc9000308ec98 R08: 74707572726f6320 R09: 203a6e6920646574
R10: 206c656e72654b20 R11: 7369206b63617473 R12: ffffffff8c0995ef
R13: dffffc0000000000 R14: ffffffff93195b80 R15: ffffffff8c0995c0
FS:  00007f0a7a93f6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffee CR3: 000000002ec20000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 vscnprintf+0x42/0x90 lib/vsprintf.c:2930
 panic+0x245/0x880 kernel/panic.c:342
 __stack_chk_fail+0x15/0x20 kernel/panic.c:836
 exc_general_protection+0x5ac/0x5d0
 </TASK>
Modules linked in:
CR2: 0000000000000018
---[ end trace 0000000000000000 ]---
RIP: 0010:0x18
Code: Unable to access opcode bytes at 0xffffffffffffffee.
RSP: 0018:ffffc9000308eba0 EFLAGS: 00010002
RAX: ffffffff93195b80 RBX: 000000000000002f RCX: ffffffff8bb86308
RDX: 000000000000000f RSI: ffffffff8c0995e0 RDI: ffffffff93195ba0
RBP: ffffc9000308ec98 R08: 74707572726f6320 R09: 203a6e6920646574
R10: 206c656e72654b20 R11: 7369206b63617473 R12: ffffffff8c0995ef
R13: dffffc0000000000 R14: ffffffff93195b80 R15: ffffffff8c0995c0
FS:  00007f0a7a93f6c0(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffee CR3: 000000002ec20000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/22 09:38 linux-next 6a7917c89f21 ca02180f .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root BUG: scheduling while atomic in __stack_chk_fail
2024/08/21 02:49 linux-next bb1b0acdcd66 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root BUG: scheduling while atomic in __stack_chk_fail
2024/08/22 19:20 linux-next 6a7917c89f21 295a4b50 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root BUG: spinlock recursion in __stack_chk_fail
* Struck through repros no longer work on HEAD.