From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f205.google.com (mail-oi1-f205.google.com [209.85.167.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1D222329367 for ; Thu, 25 Jun 2026 01:08:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.205 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782349702; cv=none; b=l0MjWG5YxD8+IBBbilvkNdE7Lx+KhbXLJmhVIflhF+si/r/j3VJiQO7DTvBeCSZsTxtIMaklLpFTE5QmoLNtcy/mMtfx5rr6Nipd50hxoAuPhieiaatr8XC6MP4XU+0LgSCk5+7RN3/XeijBGpVidswFNzrLrgEcsvJnXvUBwHs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782349702; c=relaxed/simple; bh=VZzVcoizqWYXsjm/+GxwpCnxPlnrjjh+PjCAw+ZDnmo=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=fsbCQ5RSER7Bsk+Ex5bQ46tryRlEXtHjON0aESBVAxjA/fcNGlmw4VsYRLZYKMAWRuM11o3CCzKtHnq68gXxB81cReBP0ooDKrRSgT6+SbrUvoE9JYsZDwgK6U0QaNM8oQVMGHLmaD78he7aewmlQCEcyujs68sIvIzI8uMnaws= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.167.205 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-oi1-f205.google.com with SMTP id 5614622812f47-48952d1c293so2457445b6e.3 for ; Wed, 24 Jun 2026 18:08:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1782349700; x=1782954500; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=oWKNY6CujSibhry+4PJ7L0fdyDs1eNvDG+6EaM2I4T0=; b=sPy/Si1v6yeIzuickNIXgD7gxvqRiwEI3p4UQv/Srgkt6zjrwV8NeBmzbXKIv6rFlM yLu+gF2iARVLwcWPaN7gpIbqmihqyF9nI2sastHE4bvfx8ZWq0zwH5z0JbiV9maOExSX w4f81x20Y25GKOxM4TUZOlBavSf/ozETytsfaUdJU4NzF6L7dmfQdj3NSByWvedON4zn XUUHhfeERMIlmwR5g7mZCs+mJI6e6UwNCt9+MaUXrF76cAukQoFeBdeRnx6Z3kB2ZxKY JsNCtM0cvPMtSIEe60IPB8WCEquh39u7dZ1H3Ol2kymFv9eEosQZy0y4wIXUG8K3Gltu xMpQ== X-Gm-Message-State: AOJu0YxZsL3eyjedNp82uGVx042JiOL55V8CuPQcc3c7IukUZQsGk4+X cpG20SUWUP24m5CjDOncpImry8XOeDd68eYENYjA18EjhIZtLcjC/fXrMoN8UkhEqxUuS5QhCrx 33tVG5GCl4Rta/CyxUKAh2l0IEV3FjLQRdhxONMVUdx0kmCvvuo9ZptYXHsO2kQ== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6808:1821:b0:489:34da:f600 with SMTP id 5614622812f47-49216248e60mr534461b6e.11.1782349700170; Wed, 24 Jun 2026 18:08:20 -0700 (PDT) Date: Wed, 24 Jun 2026 18:08:20 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a3c7f84.43b4ff68.30a095.0003.GAE@google.com> Subject: [syzbot] [kernel?] KMSAN: kernel-infoleak in exc_page_fault From: syzbot To: linux-kernel@vger.kernel.org, luto@kernel.org, peterz@infradead.org, syzkaller-bugs@googlegroups.com, tglx@kernel.org Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 9ecfb2f7287a Merge tag 'trace-ring-buffer-v7.2' of git://g.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1471e8ea580000 kernel config: https://syzkaller.appspot.com/x/.config?x=a9e1383387f0e112 dashboard link: https://syzkaller.appspot.com/bug?extid=411634dace73dad6f4d4 compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/c8d222bd96ba/disk-9ecfb2f7.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/629368d40b7e/vmlinux-9ecfb2f7.xz kernel image: https://storage.googleapis.com/syzbot-assets/156086f5f12a/bzImage-9ecfb2f7.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+411634dace73dad6f4d4@syzkaller.appspotmail.com BUG: KMSAN: kernel-infoleak in rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline] BUG: KMSAN: kernel-infoleak in rseq_update_usr include/linux/rseq_entry.h:536 [inline] BUG: KMSAN: kernel-infoleak in rseq_exit_user_update include/linux/rseq_entry.h:645 [inline] BUG: KMSAN: kernel-infoleak in __rseq_exit_to_user_mode_restart include/linux/rseq_entry.h:674 [inline] BUG: KMSAN: kernel-infoleak in rseq_exit_to_user_mode_restart include/linux/rseq_entry.h:703 [inline] BUG: KMSAN: kernel-infoleak in exit_to_user_mode_loop kernel/entry/common.c:103 [inline] BUG: KMSAN: kernel-infoleak in __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline] BUG: KMSAN: kernel-infoleak in irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:244 [inline] BUG: KMSAN: kernel-infoleak in irqentry_exit_to_user_mode include/linux/irq-entry-common.h:315 [inline] BUG: KMSAN: kernel-infoleak in irqentry_exit+0x4a6/0xa40 kernel/entry/common.c:165 exc_page_fault+0x7e/0xb0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x2b/0x30 arch/x86/include/asm/idtentry.h:595 Local variable st.i.i created at: __do_sys_statfs fs/statfs.c:193 [inline] __se_sys_statfs fs/statfs.c:191 [inline] __x64_sys_statfs+0x73/0x200 fs/statfs.c:191 x64_sys_call+0x334c/0x3ea0 arch/x86/include/generated/asm/syscalls_64.h:138 Bytes 0-3 of 4 are uninitialized Memory access of size 4 starts at ffff88811856be78 Data copied to user address 00007ff99a04cac0 CPU: 1 UID: 0 PID: 5314 Comm: rm Not tainted syzkaller #0 PREEMPT(lazy) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026 ===================================================== --- 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