From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id E26AE42A82
	for <linux-kernel@vger.kernel.org>; Wed,  3 Jun 2026 09:39:33 +0000 (UTC)
Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18
ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116;
	t=1780479574; cv=none; b=S8biXL9I0SXAlGqrn/CeTPl9Wpp0XHO76wgz7/q1VTTUvWbFkJms6lvw13U+6d/XQzoPHqmRVQd+9VVA4pm+TsA8Jp5tmzsOp1XzMyUJV0dagQMDF6bHsrT+0qbTIYNp6OazNkHUPTuWWikjTcxPsqHJaEsUlhstpabtzeuyU90=
ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org;
	s=arc-20240116; t=1780479574; c=relaxed/simple;
	bh=IFUwuPopYaTYofs/0Ehk92riqtqXWIFTsXmEHHifZgU=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:Content-Disposition:In-Reply-To; b=WPFpu9V8+4VU+11FNSUPTuuHJ1RrdShoY6TNEK9pYZWJt2DJjqa6IvlS1fa6G+rDD3JN9M6JrVga8eGHl0p8xP38laOKhFfSEgyGq6++J5GCeQ5FRXBecElM5o9FUVlueNM1BdMZRhVK0lf71+cchebh8+/TH69XS8dsLIzmgy8=
ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Tgdx6a3l; arc=none smtp.client-ip=100.103.45.18
Authentication-Results: smtp.subspace.kernel.org;
	dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Tgdx6a3l"
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 34A031F00898;
	Wed,  3 Jun 2026 09:39:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org;
	s=k20260515; t=1780479573;
	bh=zuq5ersmXoZ0pED0aXddD3WV95bivofIOARkffoDvpw=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To;
	b=Tgdx6a3lQZDTGZR5gx1bSr14cZUoNlk2SCrLgOiyw9tc0JIZFVxIWrRolzaZC42GP
	 7C1nwYQxpaFV6QjKP7Ma4kBuXT2X6f7f1GB/786iUT+YE/0KR+ttgjSuekJDNsm1XA
	 XjQY9L5JbUuuIydBfBKDG2hmz97BaESKJPVkhipStlewkGmlxJQWNdiOhOVl1j0A5f
	 lgyBkZPs8B06XdXNQ8bnb8pdcQamP1Ji6JARye0fajcDYjpUO2NLFIU+pCMM1twm83
	 tP4vhnyIL/8JFIhb7ct06iGk3TRvkRwjMMO963PIFzwg35BwZN4yn/CtLTXLcM2sgg
	 PFgaCboATuTAg==
Date: Wed, 3 Jun 2026 10:39:27 +0100
From: Keith Busch <kbusch@kernel.org>
To: Tianchu Chen <tianchu.chen@linux.dev>
Cc: hare@suse.de, hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet-auth: validate reply message payload bounds
 against transfer length
Message-ID: <ah_2T-VTWNjdYpbb@kbusch-mbp>
References: <f4aca9b14e74a7f7f8cd9620e13cc32a6a2b7746@linux.dev>
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f4aca9b14e74a7f7f8cd9620e13cc32a6a2b7746@linux.dev>

On Fri, May 29, 2026 at 02:18:39PM +0000, Tianchu Chen wrote:
> From: Tianchu Chen <flynnnchen@tencent.com>
> 
> nvmet_auth_reply() accesses the variable-length rval[] array using
> attacker-controlled hl (hash length) and dhvlen (DH value length) fields
> without verifying they fit within the allocated buffer of tl bytes.

Thanks, applied to nvme-7.2.