[syzbot] [kernel?] WARNING in __run_timer_base

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b320789d6883 Linux 6.17-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15a84e62580000
kernel config: https://syzkaller.appspot.com/x/.config?x=bd9738e00c1bbfb4
dashboard link: https://syzkaller.appspot.com/bug?extid=bebd7f7f6db444f08153
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dc96f2e9db93/disk-b320789d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fcbc622fd55c/vmlinux-b320789d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c309f0747b00/bzImage-b320789d.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 16 at kernel/time/timer.c:1785 expire_timers kernel/time/timer.c:1785 [inline]
WARNING: CPU: 0 PID: 16 at kernel/time/timer.c:1785 __run_timers kernel/time/timer.c:2372 [inline]
WARNING: CPU: 0 PID: 16 at kernel/time/timer.c:1785 __run_timer_base+0x777/0x970 kernel/time/timer.c:2384
Modules linked in:
CPU: 0 UID: 0 PID: 16 Comm: ktimers/0 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:expire_timers kernel/time/timer.c:1785 [inline]
RIP: 0010:__run_timers kernel/time/timer.c:2372 [inline]
RIP: 0010:__run_timer_base+0x777/0x970 kernel/time/timer.c:2384
Code: 26 4d 85 e4 74 7d e8 f8 8f 12 00 e9 48 fe ff ff e8 ee 8f 12 00 48 8b 5c 24 28 43 80 7c 3d 00 00 75 d4 eb da e8 da 8f 12 00 90 <0f> 0b 90 48 8b 44 24 40 42 80 3c 38 00 48 8b 5c 24 28 74 a9 48 89
RSP: 0018:ffffc900001579c0 EFLAGS: 00010046
RAX: ffffffff81abcef6 RBX: 0000000000000000 RCX: ffff88801ae85940
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000100
RBP: ffffc90000157b30 R08: 0000000000000000 R09: 0000000000000100
R10: dffffc0000000000 R11: fffffbfff1e3a947 R12: ffff88805c0068c0
R13: 1ffff9200002af50 R14: ffffc90000157a80 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881268c2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000008 CR3: 000000003844e000 CR4: 00000000003526f0
Call Trace:
<TASK>
run_timer_base kernel/time/timer.c:2393 [inline]
run_timer_softirq+0xb7/0x180 kernel/time/timer.c:2403
handle_softirqs+0x22c/0x710 kernel/softirq.c:579
__do_softirq kernel/softirq.c:613 [inline]
run_ktimerd+0xcf/0x190 kernel/softirq.c:1043
smpboot_thread_fn+0x542/0xa60 kernel/smpboot.c:160
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x3f9/0x770 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>


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