From: syzbot <syzbot+23d7fcd204e3837866ff@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, pardhuvarma.kernel@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KMSAN: uninit-value in irqentry_exit_to_kernel_mode_preempt
Date: Mon, 04 May 2026 07:51:02 -0700 [thread overview]
Message-ID: <69f8b256.170a0220.bb392.0002.GAE@google.com> (raw)
In-Reply-To: <CAESLoqpJEtny0jC9=DQrCZQ7AHyZRCC+y2OW5F9sc94B+cqS4Q@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in irqentry_exit_to_kernel_mode_preempt
=====================================================
BUG: KMSAN: uninit-value in irqentry_exit_to_kernel_mode_preempt+0xb0/0xc0 include/linux/irq-entry-common.h:472
irqentry_exit_to_kernel_mode_preempt+0xb0/0xc0 include/linux/irq-entry-common.h:472
irqentry_exit_to_kernel_mode include/linux/irq-entry-common.h:547 [inline]
irqentry_exit+0x7b/0x760 kernel/entry/common.c:164
sysvec_apic_timer_interrupt+0x52/0x90 arch/x86/kernel/apic/apic.c:1061
asm_sysvec_apic_timer_interrupt+0x1f/0x30 arch/x86/include/asm/idtentry.h:697
encrypted_instantiate+0x2036/0x3220 security/keys/encrypted-keys/encrypted.c:821
__key_instantiate_and_link+0xfe/0x5d0 security/keys/key.c:446
__key_create_or_update+0x12c4/0x1500 security/keys/key.c:941
key_create_or_update+0x5f/0x80 security/keys/key.c:1021
__do_sys_add_key security/keys/keyctl.c:134 [inline]
__se_sys_add_key+0x656/0x870 security/keys/keyctl.c:74
__x64_sys_add_key+0xe4/0x150 security/keys/keyctl.c:74
x64_sys_call+0xd3f/0x3ea0 arch/x86/include/generated/asm/syscalls_64.h:249
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x134/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Local variable dlen created at:
encrypted_key_alloc+0x4f/0xa70 security/keys/encrypted-keys/encrypted.c:586
encrypted_instantiate+0x45e/0x3220 security/keys/encrypted-keys/encrypted.c:812
CPU: 0 UID: 0 PID: 6537 Comm: syz.0.33 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
=====================================================
Tested on:
commit: 6d35786d Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14e5576c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1c3f61154f3bb7e5
dashboard link: https://syzkaller.appspot.com/bug?extid=23d7fcd204e3837866ff
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Note: no patches were applied.
next parent reply other threads:[~2026-05-04 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAESLoqpJEtny0jC9=DQrCZQ7AHyZRCC+y2OW5F9sc94B+cqS4Q@mail.gmail.com>
2026-05-04 14:51 ` syzbot [this message]
[not found] <CAESLoqqDdz9SZUSyYRWrQF3T1KM4MzBMm3-v9rXKcUJqaehN0w@mail.gmail.com>
2026-05-03 22:36 ` [syzbot] [kernel?] KMSAN: uninit-value in irqentry_exit_to_kernel_mode_preempt syzbot
[not found] <CAESLoqogDqVUO6oiw8iRAN0PXD_tGUWxRv8iYz3PSu1DuEeOUg@mail.gmail.com>
2026-05-03 19:49 ` syzbot
2026-04-19 15:01 syzbot
2026-05-03 13:01 ` 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=69f8b256.170a0220.bb392.0002.GAE@google.com \
--to=syzbot+23d7fcd204e3837866ff@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pardhuvarma.kernel@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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.