From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oi1-f206.google.com (mail-oi1-f206.google.com [209.85.167.206]) (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 BF68739021A for ; Fri, 24 Jul 2026 12:25:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.167.206 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784895928; cv=none; b=V7x3P/jh6r7Fn/ZEBZ7378LALrR3xAgP4FG94W013dnwreWxS8Tfkq4i3nh0T7EPciXZiUhxEv3TYWfRFCi0B3mixOJUW6kEzjJ/LwaYCrJnbOP5Ygo4ft3ddWirojovtPDSS/1l61XG15NyTT+PblrpHzCmDyAxJkcXVryqhkg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784895928; c=relaxed/simple; bh=DI2CFUoiepq485NCZW5BqEBw/Dnumny5NXyDwfHLafc=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=B8lt+nQz2YfHSOs+8XJgWDXjM6oUmE0EjKihw8rh+f+Q3N77JBmBelkGTQiOuva03e0QaWGMctMcNFA8s8pXyI3jU+FcuT22KVoEPVnObdtr6kTaYHidjQMB5AAcRIV2bof4rA8GRkHuqJ7E+VMy15FUq7gyqipd4bW+HVyKUBY= 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.206 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-f206.google.com with SMTP id 5614622812f47-4ab260600easo1672123b6e.1 for ; Fri, 24 Jul 2026 05:25:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1784895925; x=1785500725; h=content-type:to:from:subject:message-id:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=NeyzBsiEVP7wMt2NZuTVRlgaoprFj7Sofu/D4/dgBqU=; b=VdAe8xEq8uuhwC//6E7opQ/gQd8gEsbTAfZuM61r2C/6eMKWfB90Z77xdSwgx1Wzug jBzyxCsobHL6gXZL/3nYVgeBEM+5S3RWAlOBNiRpPkSg484+cYXvljN8AFe3WccFGziC 1JQRjqBAxLtfW6cLn3P42j/pI/7/kxWAmckT+RDB1Gxw6Q/rIZBmaQuZEVllw/s1lIGq LtuQMd+RGqN+/1biLtAPLYCWzQA+9y+6KJTVjeHRUC1VcXCEIaS4qVvLzauoKrQaBOIh Y+UzaaoO2uX0AYadq1hhWVF3e4Xwxc+vc9erU7wGr1hoTn5lLv66UiYAC7vajvH90pNU Fk5A== X-Gm-Message-State: AOJu0YxEOYXzym2j5qtUdYx1Q1Aepc7UnfiB6Qw5NAU+sZcGw2QTLwfR mChQonx74DcD+zDhQzO/DG02x/VZMpga9ONAX+4Q3iXXq8hI9Lc+A/aEQsZTALhJI26db55IOOq etXxDAGNHpa5gWwbv3ToNAkUV86g8BkPorfqkwyBv/uftBCB2xOarVck1aA7uUA== 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:1b0b:b0:485:7c46:b866 with SMTP id 5614622812f47-4ab5e50e50fmr229554b6e.16.1784895925665; Fri, 24 Jul 2026 05:25:25 -0700 (PDT) Date: Fri, 24 Jul 2026 05:25:25 -0700 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <6a6359b5.dde6c935.cf6c8.0021.GAE@google.com> Subject: [syzbot] [kernel?] KMSAN: kernel-infoleak in irqentry_exit (3) 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: 4a50a141f05a Merge tag 'bootconfig-fixes-v7.2-rc1' of git:.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13c87bb1580000 kernel config: https://syzkaller.appspot.com/x/.config?x=c2842025f4a17812 dashboard link: https://syzkaller.appspot.com/bug?extid=fb19c2cd5a21000b7336 compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/c4b66817b655/disk-4a50a141.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/ce2987914219/vmlinux-4a50a141.xz kernel image: https://storage.googleapis.com/syzbot-assets/61031b19febb/bzImage-4a50a141.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+fb19c2cd5a21000b7336@syzkaller.appspotmail.com 8021q: adding VLAN 0 to HW filter on device bond0 eql: remember to turn off Van-Jacobson compression on your slave devices ===================================================== 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 rseq_set_ids_get_csaddr include/linux/rseq_entry.h:502 [inline] rseq_update_usr include/linux/rseq_entry.h:536 [inline] rseq_exit_user_update include/linux/rseq_entry.h:645 [inline] __rseq_exit_to_user_mode_restart include/linux/rseq_entry.h:674 [inline] rseq_exit_to_user_mode_restart include/linux/rseq_entry.h:703 [inline] exit_to_user_mode_loop kernel/entry/common.c:103 [inline] __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline] irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:244 [inline] irqentry_exit_to_user_mode include/linux/irq-entry-common.h:315 [inline] 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 agg.tmp11.i.i.i created at: class_fd_constructor include/linux/file.h:83 [inline] __sys_getsockopt net/socket.c:2497 [inline] __do_sys_getsockopt net/socket.c:2512 [inline] __se_sys_getsockopt net/socket.c:2509 [inline] __x64_sys_getsockopt+0xdb/0x4f0 net/socket.c:2509 x64_sys_call+0x3ab8/0x3ea0 arch/x86/include/generated/asm/syscalls_64.h:56 Bytes 1-3 of 4 are uninitialized Memory access of size 4 starts at ffff88811c49fe78 Data copied to user address 00007fc26f35e680 CPU: 0 UID: 0 PID: 5226 Comm: dhcpcd Not tainted syzkaller #0 PREEMPT(lazy) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/16/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