Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp5429881ybf; Thu, 5 Mar 2020 00:30:28 -0800 (PST) X-Google-Smtp-Source: ADFU+vukh06e2gwj4hrEEm0+a/u3YKcutcS8t75z6uq4faGNfLJpLz4EEMtjewKMohQPQiFfPtNM X-Received: by 2002:a05:6830:30b2:: with SMTP id g18mr3064093ots.343.1583397028527; Thu, 05 Mar 2020 00:30:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583397028; cv=none; d=google.com; s=arc-20160816; b=k40RTQ/9/UAkndyIUE6x79HLyq8ZTkLgHYjTjNe16L9WOvZCezgUz37dMkHkWRIQh0 qg1ZUGcYRn8+kfXSl3KGDAuryBxqNVGDzBnb3rPZQ1hNUwgmZ+YgTqdQ7BS8nkdEgI0w uYO5ESAlYQ8JHbmZFAd4knBrM3NQprs+1UUgHy3nmB/MwVBQciRsf061w5HlmM/DDKgy 71FgfXLi+b4ITvsWzlkpaZiTHrrUho9zK5J4FI0jNIr0BK2vppJVl/NBbbNcEdFXBSyh hw438yO11q/9mQDuKjT5XWBThjFecCwSqQqnS6pd313Bpv5rTFrTiVcRe76ubMRPQR8/ yTjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from; bh=TjQUjoV9CrSje8nKffjkANDvunj5OHJXipHWlgNXKGQ=; b=nygmQ4kh43QolBuKV4bk6swm1BS3JdYeDUKcpVcblPbiirTS3uVexA4v2qeZZAIKpX ac/vLJ2Mp6gQdXcir4Aqm9OVqMNvyzX3ZA21p79PP9Z/onVPSLQk5zRTPrxcA8nA0FXi N3Y13pxbzX6IT5nP/F5zRaDsaQrdgEZlkJXX9zntEjxbNNSYoLJtv1Yo35wjk2VXbhio sgqbm4226fEMT/PFuJV/v+WfPhvkPFqcCEHNEjGS20l71zsE8yMO9N60wP4sNYQFwsxb Qu7W0vnDC2nSgRcIEMRHE3+LGOF6XdvABE2MmqGZJ3WWIlIQGDlGZai6rp9r05nrEdiQ lK4Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z16si3095162oia.151.2020.03.05.00.30.16; Thu, 05 Mar 2020 00:30:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725924AbgCEIaB (ORCPT + 99 others); Thu, 5 Mar 2020 03:30:01 -0500 Received: from szxga05-in.huawei.com ([45.249.212.191]:11169 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725880AbgCEIaB (ORCPT ); Thu, 5 Mar 2020 03:30:01 -0500 Received: from DGGEMS405-HUB.china.huawei.com (unknown [172.30.72.58]) by Forcepoint Email with ESMTP id C618C65B5E46CE54B206; Thu, 5 Mar 2020 16:29:58 +0800 (CST) Received: from fedora-aep.huawei.cmm (10.175.113.49) by DGGEMS405-HUB.china.huawei.com (10.3.19.205) with Microsoft SMTP Server id 14.3.439.0; Thu, 5 Mar 2020 16:29:50 +0800 From: yangerkun To: , CC: , , Subject: [PATCH 4.4.y v2] crypto: algif_skcipher - use ZERO_OR_NULL_PTR in skcipher_recvmsg_async Date: Thu, 5 Mar 2020 16:57:55 +0800 Message-ID: <20200305085755.22730-1-yangerkun@huawei.com> X-Mailer: git-send-email 2.17.2 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.175.113.49] X-CFilter-Loop: Reflected Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Nowdays, we trigger a oops: ... kasan: GPF could be caused by NULL-ptr deref or user memory accessgeneral protection fault: 0000 [#1] SMP KASAN ... Call Trace: [] skcipher_recvmsg_async+0x3f1/0x1400 x86/../crypto/algif_skcipher.c:543 [] skcipher_recvmsg+0x93/0x7f0 x86/../crypto/algif_skcipher.c:723 [] sock_recvmsg_nosec x86/../net/socket.c:702 [inline] [] sock_recvmsg x86/../net/socket.c:710 [inline] [] sock_recvmsg+0x94/0xc0 x86/../net/socket.c:705 [] sock_read_iter+0x27b/0x3a0 x86/../net/socket.c:787 [] aio_run_iocb+0x21b/0x7a0 x86/../fs/aio.c:1520 [] io_submit_one x86/../fs/aio.c:1630 [inline] [] do_io_submit+0x6b9/0x10b0 x86/../fs/aio.c:1688 [] SYSC_io_submit x86/../fs/aio.c:1713 [inline] [] SyS_io_submit+0x2d/0x40 x86/../fs/aio.c:1710 [] tracesys_phase2+0x90/0x95 In skcipher_recvmsg_async, we use '!sreq->tsg' to determine does we calloc fail. However, kcalloc may return ZERO_SIZE_PTR, and with this, the latter sg_init_table will trigger the bug. Fix it be use ZERO_OF_NULL_PTR. This function was introduced with ' commit a596999b7ddf ("crypto: algif - change algif_skcipher to be asynchronous")', and has been removed with 'commit e870456d8e7c ("crypto: algif_skcipher - overhaul memory management")'. Reported-by: Hulk Robot Signed-off-by: yangerkun --- crypto/algif_skcipher.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) v1->v2: update the commit message diff --git a/crypto/algif_skcipher.c b/crypto/algif_skcipher.c index d12782dc9683..9bd4691cc5c5 100644 --- a/crypto/algif_skcipher.c +++ b/crypto/algif_skcipher.c @@ -538,7 +538,7 @@ static int skcipher_recvmsg_async(struct socket *sock, struct msghdr *msg, lock_sock(sk); tx_nents = skcipher_all_sg_nents(ctx); sreq->tsg = kcalloc(tx_nents, sizeof(*sg), GFP_KERNEL); - if (unlikely(!sreq->tsg)) + if (unlikely(ZERO_OR_NULL_PTR(sreq->tsg))) goto unlock; sg_init_table(sreq->tsg, tx_nents); memcpy(iv, ctx->iv, ivsize); -- 2.17.2