[v5.15] WARNING in irqentry_enter_from_user_mode

Hello,

syzbot found the following issue on:

HEAD commit: c16c81c81336 Linux 5.15.178
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=149a65a8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d302c69e93fb6774
dashboard link: https://syzkaller.appspot.com/bug?extid=24d62ac3e2e098584be2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/267e46ee7273/disk-c16c81c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/944e289206cf/vmlinux-c16c81c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f8cadf62458e/bzImage-c16c81c8.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

------------[ cut here ]------------
WARNING: CPU: 1 PID: 4352 at kernel/entry/common.c:21 arch_static_branch arch/x86/include/asm/jump_label.h:27 [inline]
WARNING: CPU: 1 PID: 4352 at kernel/entry/common.c:21 context_tracking_enabled include/linux/context_tracking_state.h:31 [inline]
WARNING: CPU: 1 PID: 4352 at kernel/entry/common.c:21 ct_state include/linux/context_tracking.h:97 [inline]
WARNING: CPU: 1 PID: 4352 at kernel/entry/common.c:21 __enter_from_user_mode kernel/entry/common.c:21 [inline]
WARNING: CPU: 1 PID: 4352 at kernel/entry/common.c:21 irqentry_enter_from_user_mode+0x14/0x40 kernel/entry/common.c:314
Modules linked in:
CPU: 1 PID: 4352 Comm: syz.3.26 Not tainted 5.15.178-syzkaller #0
WARNING: stack going in the wrong direction? at asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:600
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:__enter_from_user_mode kernel/entry/common.c:21 [inline]
RIP: 0010:irqentry_enter_from_user_mode+0x14/0x40 kernel/entry/common.c:314
Code: eb b6 65 8b 05 ed f4 c3 75 85 c0 0f 84 e3 fd ff ff eb 83 0f 1f 00 48 8b 3c 24 e8 67 f1 ff ff eb 07 eb 0b e9 ae a6 47 f7 eb 13 <0f> 0b eb f3 bf 01 00 00 00 e8 2e 03 00 00 e9 99 a6 47 f7 65 8b 05
RSP: 0018:ffffc9000337fe18 EFLAGS: 00010097
==================================================================
BUG: KASAN: stack-out-of-bounds in __show_regs+0x7e/0x500 arch/x86/kernel/process_64.c:81
Read of size 8 at addr ffffc9000337fdb8 by task syz.3.26/4352

CPU: 1 PID: 4352 Comm: syz.3.26 Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
print_address_description+0x63/0x3b0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x16b/0x1c0 mm/kasan/report.c:451
__show_regs+0x7e/0x500 arch/x86/kernel/process_64.c:81
show_regs+0x32/0x60 arch/x86/kernel/dumpstack.c:472
__warn+0x15b/0x300 kernel/panic.c:678
report_bug+0x1b7/0x2e0 lib/bug.c:199
handle_bug+0x3d/0x70 arch/x86/kernel/traps.c:239
exc_invalid_op+0x16/0x40 arch/x86/kernel/traps.c:259
asm_exc_invalid_op+0x16/0x20 arch/x86/include/asm/idtentry.h:604
RIP: 0010:__enter_from_user_mode kernel/entry/common.c:21 [inline]
RIP: 0010:irqentry_enter_from_user_mode+0x14/0x40 kernel/entry/common.c:314
Code: eb b6 65 8b 05 ed f4 c3 75 85 c0 0f 84 e3 fd ff ff eb 83 0f 1f 00 48 8b 3c 24 e8 67 f1 ff ff eb 07 eb 0b e9 ae a6 47 f7 eb 13 <0f> 0b eb f3 bf 01 00 00 00 e8 2e 03 00 00 e9 99 a6 47 f7 65 8b 05
RSP: 0018:ffffc9000337fe18 EFLAGS: 00010097
RAX: 0000000000000000 RBX: ffffc9000337ff58 RCX: 0000000000000000
RDX: 00000000000000a8 RSI: ffffffff8aab2b80 RDI: ffffffff8af9f2c0
RBP: ffffc9000337ff48 R08: dffffc0000000000 R09: fffff52000670000
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 000000000000000c
irqentry_enter+0xf/0x50 kernel/entry/common.c:332
exc_general_protection+0x32/0x4f0 arch/x86/kernel/traps.c:562
asm_exc_general_protection+0x22/0x30 arch/x86/include/asm/idtentry.h:600
</TASK>

KASAN internal error: frame info validation failed; invalid marker: 0

Memory state around the buggy address:
ffffc9000337fc80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffffc9000337fd00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffffc9000337fd80: 00 00 00 00 f1 f1 f1 f1 04 f3 f3 f3 00 00 00 00
^
ffffc9000337fe00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffffc9000337fe80: f1 f1 f1 f1 00 00 f3 f3 00 00 00 00 00 00 00 00
==================================================================


---
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 [email protected].

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

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.