From nobody Sat Feb 7 20:38:44 2026 Received: from mail-oa1-f72.google.com (mail-oa1-f72.google.com [209.85.160.72]) (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 3F6AF346E41 for ; Tue, 20 Jan 2026 04:33:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.160.72 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768883633; cv=none; b=Vhdsmb6GhX7QzSjS+I/xORhCqUD4cuz+1fUo6vyHL9Fy1Ap0OaspJx/10XeDVtYYKyoSKNq0iz/yOCsAxZDvi80nbjhS+dUusO0QqfDqNXeEqShp5ERXn16HCyVFhcQ3R6aAR5Wss59bblSjUHApi1Ho3REHRxMjPl5kpMzkoEM= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768883633; c=relaxed/simple; bh=tcGNW2hxVTTSfggNmH9EYgdIJgwNNZS8OOxiT6BxX8I=; h=MIME-Version:Date:In-Reply-To:Message-ID:Subject:From:To: Content-Type; b=H+YemneEOqTnVwtqnZ4UflGdjvJ6vIl57bOQyVvw0oB5tZwBGxH8Vd8nb3KL5nDdkvNVIig+cRvT6E++7vwELoXrBKgDbOiOVvuPWyZtssjl4v3f49biYiGxi3DpGImNRoTlxXI3WBEAvId9plSA7y6aJAQNFiAlNfUvP6awiAQ= 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.160.72 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-oa1-f72.google.com with SMTP id 586e51a60fabf-4041c362f15so4802000fac.0 for ; Mon, 19 Jan 2026 20:33:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768883626; x=1769488426; h=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=xI4bNIa/59/FYLrepaqcH66BXnamwmltwoKTTzyWMiE=; b=eL7VpBDFlcWTOfeAEcWI4RSAyKTDyNRReIr5W9xIqKmhW25kvoGz5A8j5uadrryKk2 qkgNDPRdifIFBumFedd4Jr7KItyfe70k59vhCWreBceDDvkaDKmMYBf9jdbkWElk0JPF 65PpS6FDI4vwiSuuRMvpQol/NDJm5eJrI0YDQ9muakf5y4Cyr70W/vgrM67tzJbjrbg5 ZLtRnrXauFM6HN5v88XDXYLkZMI/K854T7ZynHMDLImfkcrCP6+9wkEJ4CrNNSzwJr17 NYWZ6qPKarA8TJame7feiYoigkh4i1hc1osULlm277ml99qf5djufgFngzaJy48w0JKO hpBw== X-Gm-Message-State: AOJu0YzLNbV6mDtNJhdNm7N/FXq8OoxwGK6xMmyenHqMVNH36wwP6KFK n1yR8cwBZvNfuebjgAp/5zYkNvkdVFAIFdMnvjmnCbnJNXnFup8D430VevpjxmLtYehTKXeX4X5 GlUyXKdeLyrSlz3QIHl91ZWNl8JWPvTB6Gi2ZEUq5spMam3QzrQ+7TGSp0Cg= 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:1ca1:b0:65c:ff20:a3b5 with SMTP id 006d021491bc7-662b00f159amr249091eaf.77.1768883625825; Mon, 19 Jan 2026 20:33:45 -0800 (PST) Date: Mon, 19 Jan 2026 20:33:45 -0800 In-Reply-To: <696ea368.a70a0220.34546f.04b7.GAE@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <696f05a9.a00a0220.3ad28e.0003.GAE@google.com> Subject: Forwarded: [PATCH] hfsplus: fix uninit-value in hfsplus_strcasecmp From: syzbot To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For archival purposes, forwarding an incoming command email to linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com. *** Subject: [PATCH] hfsplus: fix uninit-value in hfsplus_strcasecmp Author: kartikey406@gmail.com #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git= master Syzbot reported a KMSAN uninit-value issue in hfsplus_strcasecmp() during filesystem mount operations. The root cause is that hfsplus_find_cat() declares a local hfsplus_cat_entry variable without initialization before passing it to hfs_brec_read(). If hfs_brec_read() doesn't completely fill the entire structure (e.g., when the on-disk data is shorter than sizeof(hfsplus_cat_entry)), the padding bytes in tmp.thread.nodeName remain uninitialized. These uninitialized bytes are then copied by hfsplus_cat_build_key_uni() into the search key, and subsequently accessed by hfsplus_strcasecmp() during catalog lookups, triggering the KMSAN warning. Fix this by zeroing the tmp variable before use to ensure all padding bytes are initialized. Reported-by: syzbot+d80abb5b890d39261e72@syzkaller.appspotmail.com Closes: https://syzkaller.appspot.com/bug?extid=3Dd80abb5b890d39261e72 Signed-off-by: Deepanshu Kartikey --- fs/hfsplus/catalog.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/hfsplus/catalog.c b/fs/hfsplus/catalog.c index 02c1eee4a4b8..9c75d1736427 100644 --- a/fs/hfsplus/catalog.c +++ b/fs/hfsplus/catalog.c @@ -199,6 +199,7 @@ int hfsplus_find_cat(struct super_block *sb, u32 cnid, u16 type; =20 hfsplus_cat_build_key_with_cnid(sb, fd->search_key, cnid); + memset(&tmp, 0, sizeof(tmp)); err =3D hfs_brec_read(fd, &tmp, sizeof(hfsplus_cat_entry)); if (err) return err; --=20 2.43.0