From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-oo1-f70.google.com (mail-oo1-f70.google.com [209.85.161.70]) (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 2130E346FAE for ; Fri, 17 Apr 2026 16:21:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.161.70 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776442910; cv=none; b=MgqgqkQCow3Ek887kdXdHYzmtNb2Hi3CKOxIm7EUaqI0SSjdIlCUPEDapce3pg4Gcj8BKz7BVYMIh7+S3jfYd58mKwSUKMbfhlgsLrAHhXHkx5H/CckvCQ2U8dcc47dcsbe88yU8rGGsWhxx4TKx/w/S2HTUXPi1/M+516reM2g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776442910; c=relaxed/simple; bh=GaXSvCMdC6PJMnDJpD1+5LkiwpYQC9+2DEwEY0aGFCw=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To:Cc: Content-Type; b=rMzyA86t6s5P90la95UCX2Di4bAS26mqSpaYTw2t4fnpmFmCKj9QUK9fjmR71vuvn2f3vkp+bFlQ1J/H5EBuV0t4LMf7AOwRAK/IoGpCAJXmiFk0uXsckZYfNCo0jv8rRjaYlB8/zlIqJAJMwPGBiiO7xnAlgReA1iPOr9PQk1o= 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.161.70 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-oo1-f70.google.com with SMTP id 006d021491bc7-68e7e213adfso1509276eaf.0 for ; Fri, 17 Apr 2026 09:21:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776442908; x=1777047708; h=cc:to:from:subject:message-id:in-reply-to:date:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=naPUhJy9yEy3/mlN2cv3MwSyoCrU+UlDRruj7no1Pzc=; b=ni59OzlvAl6bMX9qZgEbBxJfLE9qRHDVGMU3vuQfwmgE6wFHgivGFno7LHiiIEOsmH btovC/gOG1EO9YS6ZnLbpxapCS738DhE+RMfXitTNH3eV2bA1wUTywAR8Pr56GBntn+S uROg0nauhIwn+N7R1Nro2b97JzzG6kkneFN0cHpC21ocDGVLFOOXPmm6RQSK49nh7tKR Ldeo9HWerIEjkBtu/6Ae6/1h+6nfy0pIjlpOIKgWFT/PVG4vYjX4Qk8wxtJOE2y2nDbg qn/1/je5YJ9Rh3KtthFXluSdU/41xnaTGbA4uee3Dk0wcEBXZVntaxxaLh7QFXRp8zdX GRig== X-Forwarded-Encrypted: i=1; AFNElJ/0VXvG7TPruZ926io+JXD361/lIrkInUrGjZl8hKs2NL8w1WRBdJTnHLXrmAkOzR4HZSzgRteNBFNO9J4=@vger.kernel.org X-Gm-Message-State: AOJu0Yy++DZALEnYNP9Y67E+2X7aOk44oAj9tI+Sk9MDJD4uXBrbM1jK LyuddZ2+vJrq2AFFWJ/xXAHG5bipd0UwcwERcTWb2Vq5Q3hl2xumtjfPjCIv2aeKOUrO42PyOMC OzYkDpi2xCz8L6YEXV6Gubwk4Hg89zN8HMCbXllRUnIYMkO/wHRbtUz39hKY= 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:6820:1514:b0:67d:e505:cf57 with SMTP id 006d021491bc7-69462eee495mr2050532eaf.50.1776442908148; Fri, 17 Apr 2026 09:21:48 -0700 (PDT) Date: Fri, 17 Apr 2026 09:21:48 -0700 In-Reply-To: <177644290581.3791540.2286061222451144900@talencesecurity.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <69e25e1c.050a0220.1de265.002e.GAE@google.com> Subject: Re: [syzbot] KMSAN: uninit-value in indx_insert_into_buffer From: syzbot To: tristmd@gmail.com Cc: tristmd@gmail.com, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="UTF-8" > #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master This crash does not have a reproducer. I cannot test it. >>>From 6a686b1fe4f68f59165fc7d2d02b621331c47ca4 Mon Sep 17 00:00:00 2001 > From: Tristan Madani > Date: Fri, 17 Apr 2026 16:15:17 +0000 > Subject: [PATCH] ntfs3: zero-initialize trailing VBN slot in index entry > allocations > indx_insert_into_buffer() and indx_delete_entry() allocate index > entries with an extra sizeof(u64) for the VBN slot using kmalloc. > The VBN slot is not explicitly initialized, leaving stale heap data > that KMSAN detects as uninit-value. > Replace kmalloc with kzalloc at both allocation sites to ensure > the trailing VBN slot is zero-initialized. > Reported-by: syzbot+2472d48b2d3b2a23a570@syzkaller.appspotmail.com > Closes: https://syzkaller.appspot.com/bug?extid=2472d48b2d3b2a23a570 > Signed-off-by: Tristan Madani > --- > fs/ntfs3/index.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > diff --git a/fs/ntfs3/index.c b/fs/ntfs3/index.c > index 97f06c2..a1d8c05 100644 > --- a/fs/ntfs3/index.c > +++ b/fs/ntfs3/index.c > @@ -1838,7 +1838,7 @@ indx_insert_into_buffer(struct ntfs_index *indx, struct ntfs_inode *ni, > return -EINVAL; > > sp_size = le16_to_cpu(sp->size); > - up_e = kmalloc(sp_size + sizeof(u64), GFP_NOFS); > + up_e = kzalloc(sp_size + sizeof(u64), GFP_NOFS); > if (!up_e) > return -ENOMEM; > memcpy(up_e, sp, sp_size); > @@ -2226,7 +2226,7 @@ static int indx_get_entry_to_replace(struct ntfs_index *indx, > goto out; > } > /* Copy the candidate entry into the replacement entry buffer. */ > - re = kmalloc(le16_to_cpu(te->size) + sizeof(u64), GFP_NOFS); > + re = kzalloc(le16_to_cpu(te->size) + sizeof(u64), GFP_NOFS); > if (!re) { > err = -ENOMEM; > goto out; > -- > 2.47.3