From: syzbot <syzbot+2a895bf937943f1666cc@syzkaller.appspotmail.com>
To: anna-maria@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de
Subject: [syzbot] [kernel?] KMSAN: uninit-value in process_timeout
Date: Fri, 15 Aug 2025 08:34:26 -0700 [thread overview]
Message-ID: <689f5382.050a0220.e29e5.001b.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 0cc53520e68b Merge tag 'probes-fixes-v6.17-rc1' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=168dbc34580000
kernel config: https://syzkaller.appspot.com/x/.config?x=80850d07adb04ea2
dashboard link: https://syzkaller.appspot.com/bug?extid=2a895bf937943f1666cc
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/cad3c74a9bc2/disk-0cc53520.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7b87febcb296/vmlinux-0cc53520.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0dd5c054303b/bzImage-0cc53520.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2a895bf937943f1666cc@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in process_timeout+0x59/0x60 kernel/time/sleep_timeout.c:27
process_timeout+0x59/0x60 kernel/time/sleep_timeout.c:27
call_timer_fn+0x4c/0x520 kernel/time/timer.c:1747
expire_timers kernel/time/timer.c:1798 [inline]
__run_timers kernel/time/timer.c:2372 [inline]
__run_timer_base+0x80f/0xd90 kernel/time/timer.c:2384
run_timer_base kernel/time/timer.c:2393 [inline]
run_timer_softirq+0x3a/0x80 kernel/time/timer.c:2403
handle_softirqs+0x166/0x6e0 kernel/softirq.c:579
__do_softirq kernel/softirq.c:613 [inline]
invoke_softirq kernel/softirq.c:453 [inline]
__irq_exit_rcu+0x66/0x180 kernel/softirq.c:680
irq_exit_rcu+0x12/0x20 kernel/softirq.c:696
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1050 [inline]
sysvec_apic_timer_interrupt+0x84/0x90 arch/x86/kernel/apic/apic.c:1050
asm_sysvec_apic_timer_interrupt+0x1f/0x30 arch/x86/include/asm/idtentry.h:702
__nr_to_section include/linux/mmzone.h:1937 [inline]
__pfn_to_section include/linux/mmzone.h:2079 [inline]
pfn_valid include/linux/mmzone.h:2161 [inline]
kmsan_virt_addr_valid arch/x86/include/asm/kmsan.h:94 [inline]
virt_to_page_or_null+0x99/0x180 mm/kmsan/shadow.c:75
kmsan_get_metadata+0xfb/0x160 mm/kmsan/shadow.c:141
kmsan_get_shadow_origin_ptr+0x4a/0xb0 mm/kmsan/shadow.c:102
get_shadow_origin_ptr mm/kmsan/instrumentation.c:38 [inline]
__msan_metadata_ptr_for_load_8+0x24/0x40 mm/kmsan/instrumentation.c:94
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:409 [inline]
batadv_nc_worker+0x11f/0x1aa0 net/batman-adv/network-coding.c:719
process_one_work kernel/workqueue.c:3236 [inline]
process_scheduled_works+0xb91/0x1d80 kernel/workqueue.c:3319
worker_thread+0xedf/0x1590 kernel/workqueue.c:3400
kthread+0xd59/0xf00 kernel/kthread.c:463
ret_from_fork+0x1e3/0x310 arch/x86/kernel/process.c:148
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
Local variable timer created at:
schedule_timeout+0x44/0x240 kernel/time/sleep_timeout.c:63
kcompactd+0x470/0x2340 mm/compaction.c:3187
CPU: 1 UID: 0 PID: 3876 Comm: kworker/u8:20 Tainted: G W 6.17.0-rc1-syzkaller-00038-g0cc53520e68b #0 PREEMPT(none)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: bat_events batadv_nc_worker
=====================================================
---
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 syzkaller@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
reply other threads:[~2025-08-15 15:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=689f5382.050a0220.e29e5.001b.GAE@google.com \
--to=syzbot+2a895bf937943f1666cc@syzkaller.appspotmail.com \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.