[Android 6.1] BUG: stack guard page was hit in corrupted

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1bb38f786569 UPSTREAM: ring-buffer: Fix a race between rea..
git tree: android14-6.1
console output: https://syzkaller.appspot.com/x/log.txt?x=1401d66d980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a8fbfddff407fc2
dashboard link: https://syzkaller.appspot.com/bug?extid=dfa077a1bb45ba25e5e2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13861891980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=163321c9980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1233e9b6e369/disk-1bb38f78.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f8c99927b783/vmlinux-1bb38f78.xz
kernel image: https://storage.googleapis.com/syzbot-assets/20f7b3d6c921/bzImage-1bb38f78.xz

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

BUG: IRQ stack guard page was hit at ffffc900001a8f98 (stack is ffffc900001a9000..ffffc900001b1000)
stack guard page: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1690 Comm: syz-executor550 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:ffffc900001a8fa0 EFLAGS: 00010086
RAX: e9344cf748fd2b00 RBX: ffff8881254192c0 RCX: ffff888120433cc0
RDX: ffffc900021e7e68 RSI: ffffc900001b0b80 RDI: ffff8881254192c0
RBP: ffffc900001a9090 R08: ffffffff819e7c34 R09: ffffed1024a832c7
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc900021e7e68
R13: 1ffff9200003521c R14: ffffc900001b0b80 R15: dffffc0000000000
FS: 00007f15e142a6c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc900001a8f98 CR3: 000000011f645000 CR4: 00000000003506a0
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:ffffc900001a8fa0 EFLAGS: 00010086
RAX: e9344cf748fd2b00 RBX: ffff8881254192c0 RCX: ffff888120433cc0
RDX: ffffc900021e7e68 RSI: ffffc900001b0b80 RDI: ffff8881254192c0
RBP: ffffc900001a9090 R08: ffffffff819e7c34 R09: ffffed1024a832c7
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc900021e7e68
R13: 1ffff9200003521c R14: ffffc900001b0b80 R15: dffffc0000000000
FS: 00007f15e142a6c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc900001a8f98 CR3: 000000011f645000 CR4: 00000000003506a0
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


---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.