[v5.15] linux-5.15.y test error: Internal error in do_notify_resume

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7a6c2d093c45 Linux 5.15.191
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16f50134580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5f873230d9f36f85
dashboard link: https://syzkaller.appspot.com/bug?extid=7bc90bf72a0babab4e2c
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/985c408e56da/disk-7a6c2d09.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/71d58ca5d3c5/vmlinux-7a6c2d09.xz
kernel image: https://storage.googleapis.com/syzbot-assets/90108dc26d5f/Image-7a6c2d09.gz.xz

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

Internal error: Oops - BTI: 0000000036000001 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4176 Comm: syz.2.124 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
pstate: 42400405 (nZcv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=jc)
pc : setup_rt_frame arch/arm64/kernel/signal.c:-1 [inline]
pc : handle_signal arch/arm64/kernel/signal.c:833 [inline]
pc : do_signal arch/arm64/kernel/signal.c:908 [inline]
pc : do_notify_resume+0x958/0x3128 arch/arm64/kernel/signal.c:946
lr : __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:244 [inline]
lr : setup_rt_frame arch/arm64/kernel/signal.c:788 [inline]
lr : handle_signal arch/arm64/kernel/signal.c:833 [inline]
lr : do_signal arch/arm64/kernel/signal.c:908 [inline]
lr : do_notify_resume+0x938/0x3128 arch/arm64/kernel/signal.c:946
sp : ffff80001f8e7be0
x29: ffff80001f8e7e00 x28: 00000000fffffff2 x27: ffff80001f8e7eb0
x26: 0000000000000001 x25: 000000001fffee20 x24: ffff80001f8e7f98
x23: 0000000000000001 x22: dfff800000000000 x21: ffff0000cc9351c0
x20: 0000000000000000 x19: 0000001fffee2000 x18: 0000000000000200
x17: 0000000000000000 x16: ffff800008041920 x15: 0000000000000002
x14: 0000000000ff0100 x13: 1ffff0000283006b x12: 0000000000ff0100
x11: 0000000000000000 x10: 0000ffffffffffff x9 : 000000001fffee20
x8 : 0000000000000000 x7 : ffff800008751230 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000001
x2 : 0000000000000008 x1 : 0000000000000001 x0 : 0000000000000000
Call trace:
setup_rt_frame arch/arm64/kernel/signal.c:788 [inline]
handle_signal arch/arm64/kernel/signal.c:833 [inline]
do_signal arch/arm64/kernel/signal.c:908 [inline]
do_notify_resume+0x958/0x3128 arch/arm64/kernel/signal.c:946
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:133 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:138 [inline]
el0_da+0x10c/0x1fc arch/arm64/kernel/entry-common.c:495
el0t_64_sync_handler+0xd8/0xe4 arch/arm64/kernel/entry-common.c:629
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9a9f0329 d503229f f9405fe8 f8000928 (14000003)
---[ end trace 0c30a02b4cfe5637 ]---
----------------
Code disassembly (best guess):
0: 9a9f0329 csel x9, x25, xzr, eq // eq = none
4: d503229f csdb
8: f9405fe8 ldr x8, [sp, #184]
c: f8000928 sttr x8, [x9]
* 10: 14000003 b 0x1c <-- trapping instruction


---
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