Received-SPF: pass (google.com: domain of linux-kernel+bounces-30361-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
Date: Thu, 18 Jan 2024 08:45:48 -0800
In-Reply-To: <000000000000e3d83a060ee5285a@google.com>
Message-ID: <0000000000007ed418060f3b1822@google.com>
Subject: Re: [syzbot] [syzbot] [nfs?] KMSAN: kernel-infoleak in
 sys_name_to_handle_at (4)
From: syzbot <syzbot+09b349b3066c2e0b1e96@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: [syzbot] [nfs?] KMSAN: kernel-infoleak in sys_name_to_handle_at (4)
Author: n.zhandarovich@fintech.ru

Try using kzalloc() instead of kmalloc() in do_sys_name_to_handle()

#syz test: https://github.com/google/kmsan.git master

---
 fs/fhandle.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/fhandle.c b/fs/fhandle.c
index 18b3ba8dc8ea..57a12614addf 100644
--- a/fs/fhandle.c
+++ b/fs/fhandle.c
@@ -36,7 +36,7 @@ static long do_sys_name_to_handle(const struct path *path,
 	if (f_handle.handle_bytes > MAX_HANDLE_SZ)
 		return -EINVAL;
 
-	handle = kmalloc(sizeof(struct file_handle) + f_handle.handle_bytes,
+	handle = kzalloc(sizeof(struct file_handle) + f_handle.handle_bytes,
 			 GFP_KERNEL);
 	if (!handle)
 		return -ENOMEM;
-- 
2.25.1