From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C54E9C433EF for ; Wed, 20 Jul 2022 09:42:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=hY28nZHAq+2cdeeT7hf94b5UAP8ikHOI+tstrPqrgEI=; b=xcLNg14rSfaMbU tFAV8SQF68rkPCMSIRB2/dVo+8p/VrCPvdDFdJWpS9A+ZY+D1zsfIkR5Uugke/2ofOQUv78YPkSv7 mcE2LEs5lQtA/mTbzg6fFR1jVjaUi8vjhMmLbH765tUqkGhOGuS0/RaqRxgCRBeUXWGkgXbn9u0Zn gHHtg0DhoHWjH+VNYcIf9FR/YVtcltEE6ZTjPUaIOyU2xZqDmCHKNcjCdjKWmj3u6NjVYsJIF+1vv nAjHYhLil+tVGquyp6zzlAwjLXLHhne/7YmaeFy4zDSZ6WL7zoQuIhQ5oxOiVAVUEqQP5cWP8C0eC SlwlrUryUMy6fJArEshg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oE6Cu-003QPr-7z; Wed, 20 Jul 2022 09:41:28 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oE6Cp-003QN0-Bp for linux-arm-kernel@lists.infradead.org; Wed, 20 Jul 2022 09:41:24 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id DD2E361AFE; Wed, 20 Jul 2022 09:41:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C183AC3411E; Wed, 20 Jul 2022 09:41:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1658310082; bh=0Uh7HU+pZdlkv+nXlUEIbOCQe7d9i8cnyad1o6EdCak=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=REyJ8w41hzygC6bjYFOTuXSBcmkl3h85awz7i5ifAyKH422K/3kkUE6nmDG7d9pxY /FITzayhhmkiQf0rGMVdT0e+OJ4BOgCIkdJhqP7yCbqbNoP3iZ7/uD/mytl0yULWBs JE2h51gok/4AbR8MKJW2msOyR+l4oNKLPvy2mpBd1I5Pgh62t3MfuxRBbGjigfz2PE dcImcQzGe6T6bxFp9boDVFxHTK4kpXKwheR5nIW0ACkZVYQNztDcDYMsGMlU+9D9Th +gaMaXSsDK4jMzORkvzHFusfBJloi9e6KesxXhRZhTChjgHNd58s9gj+dBah8rnh1f AiJxM7wu4LfdQ== Date: Wed, 20 Jul 2022 10:41:16 +0100 From: Will Deacon To: GUO Zihua Cc: linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, herbert@gondor.apana.org.au, davem@davemloft.net, catalin.marinas@arm.com, ebiggers@kernel.org Subject: Re: [PATCH v2] arm64/crypto: poly1305 fix a read out-of-bound Message-ID: <20220720094116.GC15752@willie-the-truck> References: <20220712075031.29061-1-guozihua@huawei.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220712075031.29061-1-guozihua@huawei.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220720_024123_483185_C23376E9 X-CRM114-Status: GOOD ( 20.58 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 12, 2022 at 03:50:31PM +0800, GUO Zihua wrote: > A kasan error was reported during fuzzing: [...] > This patch fixes the issue by calling poly1305_init_arm64() instead of > poly1305_init_arch(). This is also the implementation for the same > algorithm on arm platform. > > Fixes: f569ca164751 ("crypto: arm64/poly1305 - incorporate OpenSSL/CRYPTOGAMS NEON implementation") > Cc: stable@vger.kernel.org > Signed-off-by: GUO Zihua > --- > arch/arm64/crypto/poly1305-glue.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) I'm not a crypto guy by any stretch of the imagination, but Ard is out at the moment and this looks like an important fix so I had a crack at reviewing it. > diff --git a/arch/arm64/crypto/poly1305-glue.c b/arch/arm64/crypto/poly1305-glue.c > index 9c3d86e397bf..1fae18ba11ed 100644 > --- a/arch/arm64/crypto/poly1305-glue.c > +++ b/arch/arm64/crypto/poly1305-glue.c > @@ -52,7 +52,7 @@ static void neon_poly1305_blocks(struct poly1305_desc_ctx *dctx, const u8 *src, > { > if (unlikely(!dctx->sset)) { > if (!dctx->rset) { > - poly1305_init_arch(dctx, src); > + poly1305_init_arm64(&dctx->h, src); > src += POLY1305_BLOCK_SIZE; > len -= POLY1305_BLOCK_SIZE; > dctx->rset = 1; With this change, we no longer initialise dctx->buflen to 0 as part of the initialisation. Looking at neon_poly1305_do_update(), I'm a bit worried that we could land in the 'if (likely(len >= POLY1305_BLOCK_SIZE))' block, end up with len == 0 and fail to set dctx->buflen. Is this a problem, or is my ignorance showing? Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel