Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp31592641rwd; Fri, 7 Jul 2023 01:22:34 -0700 (PDT) X-Google-Smtp-Source: APBJJlEKhqI0J4NPik8SiN/zaAovyGjMEjXgQKxHGgeAHnwc6ceqblj2aWmhkcO1nbeUO8YOQEud X-Received: by 2002:a17:90a:c908:b0:262:c2a1:c029 with SMTP id v8-20020a17090ac90800b00262c2a1c029mr3981947pjt.2.1688718154676; Fri, 07 Jul 2023 01:22:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1688718154; cv=none; d=google.com; s=arc-20160816; b=PCLin/72OJYTzZ2D8NlEvvFHsyjm1f3f8yQhNP+3gyer3GS2rsy1hoPFRu8rAe+nYS qXweu7kkZS1khhEsqYccwgYBnNQcRMjhbIOWi5tO/hUQMwT42gfEwFIeaNdqAakrWqCa 54STdNMaQpAXGr3iWdf0C8OsMe4Joi11MqlvuiDyBdvIEXsf4uYV92b6XciRjMk7qBXV 7XYqULjovobtZ7A71erQ3xbN7oKLFgOhD7jo5xRI1YbU3TWDvqlOrhv4EAAcKh1xCpn/ s5+vG5h5Z+vHmc9/7ksSDQRwwlU+d4Pb9N3jTNuHnAK57oj4cGqvv8BDN8jURDesskmu xpuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-transfer-encoding :content-id:mime-version:subject:cc:to:references:in-reply-to:from :organization:dkim-signature; bh=C5Vvn7/Zahf8O8PpV8RBn0i/3MxQ2008SNSrWRPqEaM=; fh=goJ1SKlVoabrEjJB77j3nSJZKiAW1GVojrjhxDDpcTw=; b=YBA43zJzL45Js58rTJy98Owt/SogOhTcCnnTaYSqJOhk69V0pmuPEgg0ctOEeTojWk K00X5XcUMloK1NOcLwi0/C/Dk2dzQaknkSefIacfNQA4SbiW5KZ2Z8jEqv3VdToEaVsl 7MVmteCF77veXIxYTFBVBazp3JEHa9yd0p3KsNu6U/ECtw8gbHV+q2wWjesOEbu7xrHE K5E7Fvav1RJJia7QiAV7II5fMRV2ufjx6bAjP1nlZORJuuEY+v9qTZTn5zsCodG2b9VZ 7D/L1ST7Zc5JSj1VTj1Dv6E/eQcP4U+4PKc0+aVcw66fUwThHE6zZD4QQbvu7fETzh/o 4ATg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PK9euEn0; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id fz23-20020a17090b025700b00257482b1795si1563701pjb.166.2023.07.07.01.22.21; Fri, 07 Jul 2023 01:22:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=PK9euEn0; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232350AbjGGIN5 (ORCPT + 99 others); Fri, 7 Jul 2023 04:13:57 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49662 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229642AbjGGIN4 (ORCPT ); Fri, 7 Jul 2023 04:13:56 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BA7291BF8 for ; Fri, 7 Jul 2023 01:13:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1688717592; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=C5Vvn7/Zahf8O8PpV8RBn0i/3MxQ2008SNSrWRPqEaM=; b=PK9euEn0K5ifBQrx2r9/tbw4IHlfrpXPIBeikNrjtrBC3vnN5tSke6ZQrVlzln9lFUSoc5 11XmShcMln2kvYDZcHXc6/qUeyOy4FmVSpSUtOc1OPgYalN3t2l5W7pJ2OmQMu3p5LCnnY y5HVmeEGeLgvH7/7YgGY4+D4Ct+OnqU= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-619-JzFakp6IPZSo13CBecC1hA-1; Fri, 07 Jul 2023 04:13:08 -0400 X-MC-Unique: JzFakp6IPZSo13CBecC1hA-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 54B30101A528; Fri, 7 Jul 2023 08:13:08 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.195]) by smtp.corp.redhat.com (Postfix) with ESMTP id 75B85F6401; Fri, 7 Jul 2023 08:13:07 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: References: <000000000000eb827e05ffa2aa4a@google.com> To: Herbert Xu Cc: dhowells@redhat.com, syzbot , davem@davemloft.net, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com Subject: Re: [syzbot] [crypto?] KASAN: slab-out-of-bounds Write in crypto_sha3_final (2) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2225019.1688717586.1@warthog.procyon.org.uk> Content-Transfer-Encoding: quoted-printable Date: Fri, 07 Jul 2023 09:13:06 +0100 Message-ID: <2225020.1688717586@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org I'm pretty certain this is the same as: https://syzkaller.appspot.com/bug?extid=3D689ec3afb1ef07b766b2 as I sometimes see the same trace when running the reproducer from there. --- #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.gi= t master crypto: algif/hash: Fix race between MORE and non-MORE sends = The 'MSG_MORE' state of the previous sendmsg() is fetched without the socket lock held, so two sendmsg calls can race. This can be seen wit= h a large sendfile() as that now does a series of sendmsg() calls, and if = a write() comes in on the same socket at an inopportune time, it can fli= p the state. = Fix this by moving the fetch of ctx->more inside the socket lock. = Fixes: c662b043cdca ("crypto: af_alg/hash: Support MSG_SPLICE_PAGES") Reported-by: syzbot+689ec3afb1ef07b766b2@syzkaller.appspotmail.com Link: https://lore.kernel.org/r/000000000000554b8205ffdea64e@google.co= m/ Signed-off-by: David Howells cc: Herbert Xu cc: Paolo Abeni cc: "David S. Miller" cc: Eric Dumazet cc: Jakub Kicinski cc: linux-crypto@vger.kernel.org cc: netdev@vger.kernel.org diff --git a/crypto/algif_hash.c b/crypto/algif_hash.c index 0ab43e149f0e..82c44d4899b9 100644 --- a/crypto/algif_hash.c +++ b/crypto/algif_hash.c @@ -68,13 +68,15 @@ static int hash_sendmsg(struct socket *sock, struct ms= ghdr *msg, struct hash_ctx *ctx =3D ask->private; ssize_t copied =3D 0; size_t len, max_pages, npages; - bool continuing =3D ctx->more, need_init =3D false; + bool continuing, need_init =3D false; int err; = max_pages =3D min_t(size_t, ALG_MAX_PAGES, DIV_ROUND_UP(sk->sk_sndbuf, PAGE_SIZE)); = lock_sock(sk); + continuing =3D ctx->more; + if (!continuing) { /* Discard a previous request that wasn't marked MSG_MORE. */ hash_free_result(sk, ctx);