syzbot


BUG: stack guard page was hit in corrupted

Status: upstream: reported C repro on 2024/08/07 17:59
Bug presence: origin:lts
[Documentation on labels]
Reported-by: syzbot+dfa077a1bb45ba25e5e2@syzkaller.appspotmail.com
First crash: 386d, last: 91d
Bug presence (2)
Date Name Commit Repro Result
2024/08/07 lts (merge base) 909ba1f1b414 C [report] BUG: stack guard page was hit in corrupted
2024/08/07 upstream (ToT) 6a0e38264012 C Didn't crash
Similar bugs (23)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-10 BUG: stack guard page was hit in corrupted (14) -1 C error 2 1254d 1254d 0/2 closed as dup on 2022/03/24 14:58
android-5-10 BUG: stack guard page was hit in corrupted (16) -1 C error 2 1248d 1250d 0/2 closed as dup on 2022/03/30 17:23
android-5-10 BUG: stack guard page was hit in corrupted (9) -1 C error 1 1262d 1262d 0/2 closed as dup on 2022/03/16 16:28
android-5-10 BUG: stack guard page was hit in corrupted (13) -1 C error 1 1256d 1256d 0/2 closed as dup on 2022/03/22 16:23
android-5-10 BUG: stack guard page was hit in corrupted (17) -1 C error 3 1245d 1245d 0/2 closed as dup on 2022/04/04 16:48
android-5-10 BUG: stack guard page was hit in corrupted (5) -1 C error 3 1267d 1267d 0/2 closed as dup on 2022/03/11 15:58
android-5-10 BUG: stack guard page was hit in corrupted (19) -1 C 1 1238d 1238d 0/2 closed as dup on 2022/04/08 17:06
android-5-10 BUG: stack guard page was hit in corrupted (6) -1 C error 1 1266d 1266d 0/2 closed as dup on 2022/03/11 22:51
android-5-10 BUG: stack guard page was hit in corrupted (20) -1 C error 1 1236d 1236d 0/2 closed as dup on 2022/04/11 14:20
android-5-10 BUG: stack guard page was hit in corrupted (21) -1 C error 3 1222d 1223d 0/2 closed as dup on 2022/05/04 16:12
android-5-10 BUG: stack guard page was hit in corrupted (8) -1 C 1 1263d 1263d 0/2 closed as dup on 2022/03/14 15:44
android-5-10 BUG: stack guard page was hit in corrupted (4) -1 C error 1 1268d 1268d 0/2 closed as dup on 2022/03/09 18:22
android-5-10 BUG: stack guard page was hit in corrupted (7) -1 C error 1 1266d 1266d 0/2 closed as dup on 2022/03/13 15:49
android-5-10 BUG: stack guard page was hit in corrupted (18) -1 C error 1 1241d 1241d 0/2 closed as dup on 2022/04/05 20:24
android-5-10 BUG: stack guard page was hit in corrupted -1 C error 3 1297d 1333d 0/2 closed as invalid on 2022/02/28 16:10
android-5-10 BUG: stack guard page was hit in corrupted (10) -1 C error 1 1260d 1260d 0/2 closed as dup on 2022/03/17 16:45
android-5-10 BUG: stack guard page was hit in corrupted (15) -1 C error 1 1253d 1253d 0/2 closed as dup on 2022/03/25 16:30
android-5-10 BUG: stack guard page was hit in corrupted (12) -1 C done 2 1257d 1259d 0/2 closed as dup on 2022/03/21 14:57
android-5-10 BUG: stack guard page was hit in corrupted (2) -1 C error 2 1274d 1276d 0/2 closed as dup on 2022/03/02 15:48
android-5-10 BUG: stack guard page was hit in corrupted (3) -1 C error 1 1269d 1269d 0/2 closed as dup on 2022/03/09 15:36
android-5-10 BUG: stack guard page was hit in corrupted (11) -1 C error 2 1259d 1259d 0/2 closed as dup on 2022/03/18 21:48
android-5-10 BUG: stack guard page was hit in corrupted (22) -1 syz done done 1 1207d 1207d 0/2 auto-closed as invalid on 2022/08/31 02:51
android-5-10 BUG: stack guard page was hit in corrupted (23) -1 syz error error 1 808d 808d 0/2 auto-obsoleted due to no activity on 2023/09/30 03:13
Last patch testing requests (6)
Created Duration User Patch Repo Result
2025/08/08 12:33 14m retest repro android14-6.1 OK log
2025/08/08 12:33 14m retest repro android14-6.1 OK log
2025/05/30 07:45 6m retest repro android14-6.1 report log
2025/05/30 07:45 9m retest repro android14-6.1 report log
2025/03/21 02:02 6m retest repro android14-6.1 report log
2025/03/21 02:02 55m retest repro android14-6.1 report log

Sample crash report:
BUG: IRQ stack guard page was hit at ffffc8ffffffff98 (stack is ffffc90000000000..ffffc90000008000)
stack guard page: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 1636 Comm: syz-executor260 Not tainted 6.1.90-syzkaller-00130-g1bb38f786569 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:bpf_overflow_handler+0x3c/0x590 kernel/events/core.c:10178
Code: 81 ec c0 00 00 00 49 89 d4 49 89 f6 48 89 fb 65 48 8b 04 25 28 00 00 00 48 89 84 24 a0 00 00 00 49 bf 00 00 00 00 00 fc ff df <48> c7 44 24 40 b3 8a b5 41 48 c7 44 24 48 79 fd 46 86 48 c7 44 24
RSP: 0018:ffffc8ffffffffa0 EFLAGS: 00010086
RAX: f5fe0f8a6f369600 RBX: ffff888123d33840 RCX: ffff88810ef70000
RDX: ffffc900023f7918 RSI: ffffc90000007b80 RDI: ffff888123d33840
RBP: ffffc90000000090 R08: ffffffff819e7c34 R09: ffffed10247a6777
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc900023f7918
R13: 1ffff9200000001c R14: ffffc90000007b80 R15: dffffc0000000000
FS:  00007fba42ea56c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc8ffffffff98 CR3: 0000000124459000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <#DF>
 </#DF>
 <IRQ>
 </IRQ>
 <TASK>
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:bpf_overflow_handler+0x3c/0x590 kernel/events/core.c:10178
Code: 81 ec c0 00 00 00 49 89 d4 49 89 f6 48 89 fb 65 48 8b 04 25 28 00 00 00 48 89 84 24 a0 00 00 00 49 bf 00 00 00 00 00 fc ff df <48> c7 44 24 40 b3 8a b5 41 48 c7 44 24 48 79 fd 46 86 48 c7 44 24
RSP: 0018:ffffc8ffffffffa0 EFLAGS: 00010086
RAX: f5fe0f8a6f369600 RBX: ffff888123d33840 RCX: ffff88810ef70000
RDX: ffffc900023f7918 RSI: ffffc90000007b80 RDI: ffff888123d33840
RBP: ffffc90000000090 R08: ffffffff819e7c34 R09: ffffed10247a6777
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc900023f7918
R13: 1ffff9200000001c R14: ffffc90000007b80 R15: dffffc0000000000
FS:  00007fba42ea56c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc8ffffffff98 CR3: 0000000124459000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	81 ec c0 00 00 00    	sub    $0xc0,%esp
   6:	49 89 d4             	mov    %rdx,%r12
   9:	49 89 f6             	mov    %rsi,%r14
   c:	48 89 fb             	mov    %rdi,%rbx
   f:	65 48 8b 04 25 28 00 	mov    %gs:0x28,%rax
  16:	00 00
  18:	48 89 84 24 a0 00 00 	mov    %rax,0xa0(%rsp)
  1f:	00
  20:	49 bf 00 00 00 00 00 	movabs $0xdffffc0000000000,%r15
  27:	fc ff df
* 2a:	48 c7 44 24 40 b3 8a 	movq   $0x41b58ab3,0x40(%rsp) <-- trapping instruction
  31:	b5 41
  33:	48 c7 44 24 48 79 fd 	movq   $0xffffffff8646fd79,0x48(%rsp)
  3a:	46 86
  3c:	48                   	rex.W
  3d:	c7                   	.byte 0xc7
  3e:	44                   	rex.R
  3f:	24                   	.byte 0x24

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/08/07 19:21 android14-6.1 1bb38f786569 109d2082 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: stack guard page was hit in corrupted
2024/08/07 17:58 android14-6.1 1bb38f786569 109d2082 .config console log report syz / log C [disk image] [vmlinux] [kernel image] ci2-android-6-1-perf BUG: stack guard page was hit in corrupted
* Struck through repros no longer work on HEAD.