[v6.6] WARNING in mce_timer_fn

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cecd39af8a1a Linux 6.6.159
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10c03fd1580000
kernel config: https://syzkaller.appspot.com/x/.config?x=efe95d6e6ac7ee37
dashboard link: https://syzkaller.appspot.com/bug?extid=79073b9caf9f17f2fc3f
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0dd9a4d694bb/disk-cecd39af.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/424ddfa385b0/vmlinux-cecd39af.xz
kernel image: https://storage.googleapis.com/syzbot-assets/039829778ad0/bzImage-cecd39af.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 15574 at arch/x86/kernel/cpu/mce/core.c:1662 mce_timer_fn+0x273/0x2b0 arch/x86/kernel/cpu/mce/core.c:1662
Modules linked in:
CPU: 0 PID: 15574 Comm: syz.3.2727 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/2026
RIP: 0010:mce_timer_fn+0x273/0x2b0 arch/x86/kernel/cpu/mce/core.c:1662
Code: e9 7c ff ff ff e8 fd 04 52 00 e9 e1 fe ff ff e8 f3 04 52 00 48 c7 c7 40 a7 c6 8a e8 b7 f7 51 09 e9 2a ff ff ff e8 dd 04 52 00 <0f> 0b e9 00 fe ff ff e8 d1 04 52 00 48 c7 c7 e0 f7 d7 8d 4c 89 f6
RSP: 0018:ffffc90000007b68 EFLAGS: 00010246
RAX: ffffffff81358bd3 RBX: ffff8880b8d28188 RCX: ffff88807e2d5a00
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000008
RBP: 0000000000000000 R08: ffffffff8f6c5aef R09: 1ffffffff1ed8b5d
R10: dffffc0000000000 R11: fffffbfff1ed8b5e R12: 1ffff92000000f78
R13: dffffc0000000000 R14: ffffffff8caa9a30 R15: 0000000000000000
FS: 00007fdc463146c0(0000) GS:ffff8880b8c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000015030 CR3: 000000002edba000 CR4: 00000000003506f0
Call Trace:
<IRQ>
call_timer_fn+0x189/0x540 kernel/time/timer.c:1701
expire_timers kernel/time/timer.c:1752 [inline]
__run_timers+0x570/0x810 kernel/time/timer.c:2023
run_timer_softirq+0x67/0xf0 kernel/time/timer.c:2036
handle_softirqs+0x27d/0x820 kernel/softirq.c:578
__do_softirq kernel/softirq.c:612 [inline]
invoke_softirq kernel/softirq.c:452 [inline]
__irq_exit_rcu+0xd3/0x190 kernel/softirq.c:661
irq_exit_rcu+0x9/0x20 kernel/softirq.c:673
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1088 [inline]
sysvec_apic_timer_interrupt+0xa4/0xc0 arch/x86/kernel/apic/apic.c:1088
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:687
RIP: 0010:finish_task_switch+0x267/0x8f0 kernel/sched/core.c:5256
Code: 35 09 85 c0 0f 84 30 01 00 00 48 85 db 0f 85 4f 01 00 00 e9 d5 04 00 00 4c 89 e7 e8 e3 e9 3e 09 e8 2e 28 30 00 fb 4c 8b 65 b8 <49> 8d bc 24 00 16 00 00 48 89 f8 48 c1 e8 03 42 0f b6 04 30 84 c0
RSP: 0018:ffffc900030f7200 EFLAGS: 00000286
RAX: ad23b84209165900 RBX: 0000000000000000 RCX: ad23b84209165900
RDX: dffffc0000000000 RSI: ffffffff8acacfe0 RDI: ffffffff8b1d5160
RBP: ffffc900030f7250 R08: ffffffff91ff15af R09: 1ffffffff23fe2b5
R10: dffffc0000000000 R11: fffffbfff23fe2b6 R12: ffff88807e2d5a00
R13: ffff8880b8c3cf88 R14: dffffc0000000000 R15: ffff8880b8c3cd08
context_switch kernel/sched/core.c:5385 [inline]
__schedule+0x15b6/0x4660 kernel/sched/core.c:6701
preempt_schedule_common+0x82/0xc0 kernel/sched/core.c:6868
preempt_schedule+0xc0/0xd0 kernel/sched/core.c:6892
preempt_schedule_thunk+0x1a/0x30 arch/x86/entry/thunk_64.S:45
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
_raw_spin_unlock_irqrestore+0x111/0x120 kernel/locking/spinlock.c:194
spin_unlock_irqrestore include/linux/spinlock.h:406 [inline]
__wake_up_common_lock kernel/sched/wait.c:140 [inline]
__wake_up_sync_key+0x12c/0x1a0 kernel/sched/wait.c:213
__unix_dgram_recvmsg+0x4bb/0xd90 net/unix/af_unix.c:2449
sock_recvmsg_nosec+0x82/0xd0 net/socket.c:1047
____sys_recvmsg+0x4d7/0x5d0 net/socket.c:2812
___sys_recvmsg+0x214/0x590 net/socket.c:2856
do_recvmmsg+0x377/0x810 net/socket.c:2950
__sys_recvmmsg net/socket.c:3029 [inline]
__do_sys_recvmmsg net/socket.c:3052 [inline]
__se_sys_recvmmsg net/socket.c:3045 [inline]
__x64_sys_recvmmsg+0x199/0x250 net/socket.c:3045
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fdc4539e559
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fdc46314028 EFLAGS: 00000246 ORIG_RAX: 000000000000012b
RAX: ffffffffffffffda RBX: 00007fdc45626090 RCX: 00007fdc4539e559
RDX: 0000000000010106 RSI: 00002000000000c0 RDI: 0000000000000003
RBP: 00007fdc454358b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000002 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fdc45626128 R14: 00007fdc45626090 R15: 00007ffe08171c88
</TASK>
----------------
Code disassembly (best guess):
0: 35 09 85 c0 0f xor $0xfc08509,%eax
5: 84 30 test %dh,(%rax)
7: 01 00 add %eax,(%rax)
9: 00 48 85 add %cl,-0x7b(%rax)
c: db 0f fisttpl (%rdi)
e: 85 4f 01 test %ecx,0x1(%rdi)
11: 00 00 add %al,(%rax)
13: e9 d5 04 00 00 jmp 0x4ed
18: 4c 89 e7 mov %r12,%rdi
1b: e8 e3 e9 3e 09 call 0x93eea03
20: e8 2e 28 30 00 call 0x302853
25: fb sti
26: 4c 8b 65 b8 mov -0x48(%rbp),%r12
* 2a: 49 8d bc 24 00 16 00 lea 0x1600(%r12),%rdi <-- trapping instruction
31: 00
32: 48 89 f8 mov %rdi,%rax
35: 48 c1 e8 03 shr $0x3,%rax
39: 42 0f b6 04 30 movzbl (%rax,%r14,1),%eax
3e: 84 c0 test %al,%al


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