From: syzbot <syzbot+ba80855313e6fa65717a@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
sdf@fomichev.me, song@kernel.org,
syzkaller-bugs@googlegroups.com, yonghong.song@linux.dev
Subject: [syzbot] [bpf?] KMSAN: uninit-value in handle_bug
Date: Sat, 06 Dec 2025 06:30:32 -0800 [thread overview]
Message-ID: <69343e08.a70a0220.38f243.002c.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: cc25df3e2e22 Merge tag 'for-6.19/block-20251201' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16c2eab4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6c445efc9db431cb
dashboard link: https://syzkaller.appspot.com/bug?extid=ba80855313e6fa65717a
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/a1afac06cfc1/disk-cc25df3e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7bd5369ac00a/vmlinux-cc25df3e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e183dedd04c6/bzImage-cc25df3e.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+ba80855313e6fa65717a@syzkaller.appspotmail.com
------------[ cut here ]------------
=====================================================
BUG: KMSAN: uninit-value in vsnprintf+0x15d9/0x1b30 lib/vsprintf.c:2911
vsnprintf+0x15d9/0x1b30 lib/vsprintf.c:2911
vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2255
vprintk_emit+0x27b/0xc50 kernel/printk/printk.c:2402
vprintk_default+0x3f/0x50 kernel/printk/printk.c:2441
vprintk+0x36/0x50 kernel/printk/printk_safe.c:82
__warn_printf lib/bug.c:187 [inline]
__report_bug+0xa53/0xe80 lib/bug.c:240
report_bug_entry+0x148/0x1d0 lib/bug.c:265
handle_bug+0xe1/0x230 arch/x86/kernel/traps.c:430
exc_invalid_op+0x1f/0x50 arch/x86/kernel/traps.c:489
asm_exc_invalid_op+0x1f/0x30 arch/x86/include/asm/idtentry.h:616
reg_bounds_sanity_check+0x577/0x1450 kernel/bpf/verifier.c:2742
reg_set_min_max+0x3be/0x450 kernel/bpf/verifier.c:16572
check_cond_jmp_op+0x3a87/0x5380 kernel/bpf/verifier.c:17016
do_check_insn kernel/bpf/verifier.c:20441 [inline]
do_check+0x23ef/0x16a50 kernel/bpf/verifier.c:20581
do_check_common+0x2217/0x3370 kernel/bpf/verifier.c:23865
do_check_main kernel/bpf/verifier.c:23948 [inline]
bpf_check+0x1e78c/0x27610 kernel/bpf/verifier.c:25255
bpf_prog_load+0x2af6/0x3100 kernel/bpf/syscall.c:3088
__sys_bpf+0x7df/0xeb0 kernel/bpf/syscall.c:6164
__do_sys_bpf kernel/bpf/syscall.c:6274 [inline]
__se_sys_bpf kernel/bpf/syscall.c:6272 [inline]
__x64_sys_bpf+0xa4/0xf0 kernel/bpf/syscall.c:6272
x64_sys_call+0x31c3/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:322
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was stored to memory at:
vsnprintf+0x15d2/0x1b30 lib/vsprintf.c:-1
vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2255
vprintk_emit+0x27b/0xc50 kernel/printk/printk.c:2402
vprintk_default+0x3f/0x50 kernel/printk/printk.c:2441
vprintk+0x36/0x50 kernel/printk/printk_safe.c:82
__warn_printf lib/bug.c:187 [inline]
__report_bug+0xa53/0xe80 lib/bug.c:240
report_bug_entry+0x148/0x1d0 lib/bug.c:265
handle_bug+0xe1/0x230 arch/x86/kernel/traps.c:430
exc_invalid_op+0x1f/0x50 arch/x86/kernel/traps.c:489
asm_exc_invalid_op+0x1f/0x30 arch/x86/include/asm/idtentry.h:616
Local variable run_ctx.i created at:
__bpf_trace_run kernel/trace/bpf_trace.c:2063 [inline]
bpf_trace_run4+0xdf/0x590 kernel/trace/bpf_trace.c:2118
__bpf_trace_sched_switch+0x221/0x290 include/trace/events/sched.h:220
CPU: 1 UID: 0 PID: 23594 Comm: syz.7.5009 Tainted: G W syzkaller #0 PREEMPT(none)
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
=====================================================
---
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
next reply other threads:[~2025-12-06 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 14:30 syzbot [this message]
2026-03-17 6:45 ` [syzbot] [bpf?] KMSAN: uninit-value in handle_bug syzbot
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=69343e08.a70a0220.38f243.002c.GAE@google.com \
--to=syzbot+ba80855313e6fa65717a@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yonghong.song@linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox