From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-il1-f200.google.com (mail-il1-f200.google.com [209.85.166.200]) (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 E0EE821369 for ; Thu, 4 Jan 2024 12:04:25 +0000 (UTC) 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-il1-f200.google.com with SMTP id e9e14a558f8ab-35fda7cdff8so2345595ab.0 for ; Thu, 04 Jan 2024 04:04:25 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704369865; x=1704974665; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=5h4zCC2hUS/A4eGxWFau/Ir/9rP/TRBrjlRWoRrC1o8=; b=CTo2+wOLMuLBpJuH+8xbHO+oR05Q5wFXtaFY7Vae47MReC+rMaFM+VYL4Kji3S2tIV r/GKXvKcdjFCl21iPMQO0qQ/9pqHkRaE5yQ8jNWql2KW5l8PRLsROHeDP79Dc+e/S+De dUDZe3y4S/WJJXO3DLatJvsZSiZJpa5FkdLRJxIi2j3O9lQ1LadHyll8mIYv3n3lhmWz x3vEkrZZ+Z4ftsP4Gfca0lYeRIniwathTrDoFm6222JHmoGN/NzlhM/7etJKY+MAD9u+ 0OCx/LD1o4WZ0JahZ4zTkBIiuRdb01AlAX2B/YN5V4dp9f4FbFy71U2Hz8Nf5hq2x+e2 toCw== X-Gm-Message-State: AOJu0YyAD98as7I597qLmo9gOGDZqQ9xPPAYog0o/GWfnfZzU2sgKhyr rwJchTuWZo3dErTiQ4TBGsNWgK6KZuUCq3dOKYRx4xIF/X6H X-Google-Smtp-Source: AGHT+IEpRdYEUpk+QhT8i+5s3rd/dbOy04wsTYq0jFBu6zIyiwxN5sLmfhVs+S11QU0A2JGZ1WH88c+DRE7pk+Bm7MDN3UCGPqZo Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1a2a:b0:35f:f683:f76b with SMTP id g10-20020a056e021a2a00b0035ff683f76bmr75190ile.3.1704369865137; Thu, 04 Jan 2024 04:04:25 -0800 (PST) Date: Thu, 04 Jan 2024 04:04:25 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <00000000000060a6c9060e1d8851@google.com> Subject: [syzbot] [ntfs3?] KMSAN: kernel-infoleak in listxattr From: syzbot To: almaz.alexandrovich@paragon-software.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 8735c7c84d1b Merge tag '6.7rc7-smb3-srv-fix' of git://git... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=11dec9a1e80000 kernel config: https://syzkaller.appspot.com/x/.config?x=d4130d4bb32c48ef dashboard link: https://syzkaller.appspot.com/bug?extid=608044293020556ff16b compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/03cd0531b6f3/disk-8735c7c8.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/6bb4ebecaed0/vmlinux-8735c7c8.xz kernel image: https://storage.googleapis.com/syzbot-assets/e40c5a86a2b5/bzImage-8735c7c8.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+608044293020556ff16b@syzkaller.appspotmail.com ===================================================== BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline] BUG: KMSAN: kernel-infoleak in _copy_to_user+0xbc/0x100 lib/usercopy.c:40 instrument_copy_to_user include/linux/instrumented.h:114 [inline] _copy_to_user+0xbc/0x100 lib/usercopy.c:40 copy_to_user include/linux/uaccess.h:191 [inline] listxattr+0x2e9/0x6a0 fs/xattr.c:843 path_listxattr fs/xattr.c:865 [inline] __do_sys_listxattr fs/xattr.c:877 [inline] __se_sys_listxattr fs/xattr.c:874 [inline] __x64_sys_listxattr+0x16b/0x2e0 fs/xattr.c:874 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Uninit was stored to memory at: ntfs_list_ea fs/ntfs3/xattr.c:232 [inline] ntfs_listxattr+0x5d2/0x8d0 fs/ntfs3/xattr.c:733 vfs_listxattr fs/xattr.c:494 [inline] listxattr+0x1f0/0x6a0 fs/xattr.c:841 path_listxattr fs/xattr.c:865 [inline] __do_sys_listxattr fs/xattr.c:877 [inline] __se_sys_listxattr fs/xattr.c:874 [inline] __x64_sys_listxattr+0x16b/0x2e0 fs/xattr.c:874 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Uninit was created at: slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768 slab_alloc_node mm/slub.c:3478 [inline] __kmem_cache_alloc_node+0x5c9/0x970 mm/slub.c:3517 __do_kmalloc_node mm/slab_common.c:1006 [inline] __kmalloc+0x121/0x3c0 mm/slab_common.c:1020 kmalloc include/linux/slab.h:604 [inline] ntfs_read_ea+0x78c/0x10b0 fs/ntfs3/xattr.c:118 ntfs_list_ea fs/ntfs3/xattr.c:204 [inline] ntfs_listxattr+0x173/0x8d0 fs/ntfs3/xattr.c:733 vfs_listxattr fs/xattr.c:494 [inline] listxattr+0x1f0/0x6a0 fs/xattr.c:841 path_listxattr fs/xattr.c:865 [inline] __do_sys_listxattr fs/xattr.c:877 [inline] __se_sys_listxattr fs/xattr.c:874 [inline] __x64_sys_listxattr+0x16b/0x2e0 fs/xattr.c:874 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Bytes 26-31 of 63 are uninitialized Memory access of size 63 starts at ffff888103174b40 Data copied to user address 0000000020000080 CPU: 0 PID: 5727 Comm: syz-executor.4 Not tainted 6.7.0-rc7-syzkaller-00029-g8735c7c84d1b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 ===================================================== --- 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