Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1053117ybx; Wed, 30 Oct 2019 09:08:51 -0700 (PDT) X-Google-Smtp-Source: APXvYqzZYqFM0DjgZ5b59G6SGLrnZpVOAsjmnaPXJKLzBm9k9UP6VcebeZ8BpmoxauqQCouDkZXa X-Received: by 2002:a7b:c101:: with SMTP id w1mr240671wmi.130.1572451730998; Wed, 30 Oct 2019 09:08:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572451730; cv=none; d=google.com; s=arc-20160816; b=FUFvzOiK5ePT699uCnVzlMOSQl34TUVt1Aj3hST7oFXlEjla6Jw14jheIO6Fn4NgxU cmEdxrJZ/uo57ep7rj0gQDYaK5UjsHf7Yztb+Mc+YFKsWPcPkVJaSAUGVMbCq9ft5YpQ 1RN7HoDX2yKiBfmxYImEQ1qI2WAV/yplnHQNT0BpluA0vWA+C6tPFnkN8kI8BMhMKinA UZ6EaOtHREo2U4jaZk5UyaC/sH+jWmoXgIr+98kvwIRnY8RSidOeOzPm5s4qi8G8Ahox Y16FTvpXFBpGsqaeUzKI9r42NZz6vqz00VUu2DL7b/ATNOkxERXHwJEeoMJ/zH8I/8uU wqTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:dkim-signature; bh=CgvHwbo+NNRECegWRGyqCvpNWgkabG1Mje5YCQX5qTY=; b=vpGEU5Kvo6e7omd7eU/GkR28O93bp9nlhims4scc2xQP0YmSY1uVtB8L3lpJdU+ilB a9tX1HMkMODIaorTlkoabI0dP4Lb4VbseV6cZBywgWu/er3NGfYRXOFl0T4xHV943N6o 9OiyKZ4L/WSa7FW+9Iq5JBB9M9OC+q2IgDCK5OI0EOvF5GRH7gySgYot1CkxB2iG+SBE cNRHzdVIjF11WEATeiGTFgexnmcavE5ugPToPwqpB2M0n2OKBDQoj5FdBM9jqr+P/82a jUK6Bxo9fgnEZM63NPsM/JGDWj/L8EcWz36zzdxOXXTJNhgaMSvdR2hXptDs08C05IpM TU6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b=2SHbxw9J; 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 g3si1796489edb.298.2019.10.30.09.08.25; Wed, 30 Oct 2019 09:08:50 -0700 (PDT) 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; dkim=pass header.i=@netronome-com.20150623.gappssmtp.com header.s=20150623 header.b=2SHbxw9J; 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 S1727162AbfJ3QIY (ORCPT + 99 others); Wed, 30 Oct 2019 12:08:24 -0400 Received: from mail-pl1-f195.google.com ([209.85.214.195]:46348 "EHLO mail-pl1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726841AbfJ3QIY (ORCPT ); Wed, 30 Oct 2019 12:08:24 -0400 Received: by mail-pl1-f195.google.com with SMTP id q21so1179849plr.13 for ; Wed, 30 Oct 2019 09:08:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netronome-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=CgvHwbo+NNRECegWRGyqCvpNWgkabG1Mje5YCQX5qTY=; b=2SHbxw9J5M7HFw9jDPEI0KMR76luYm9dP3fkBGJuU4hBe2siNSP0VsR8nNUskGLQOl ChmcEnGsLS423KRh7rS7id0EBAgntELZDtsLjyLEmk06umElsJn8I1wgz/t4+5Oe3z/K cGi20pgETz94OedP5LcS6dIZEQ0eSMwyoD/uWTpHkKVWR0yDuvMPdE4fkZVVTHoX7CBY PnYZ5PQeCf8XNUDv4H5x7k0HVmnyA/4NBs91YM8eADKf5EbkLe8uYpFeYcoWBQPFpZ4c Oo1OTiVS1ipggsNhDtv27IMl86AonjGT8eP7mvGo+woiuQxRJqVGvY4AY1c91brQFez6 rsKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=CgvHwbo+NNRECegWRGyqCvpNWgkabG1Mje5YCQX5qTY=; b=hcijqH1tNxE0KRv/Vz+pCPEy/5yTP3/+VfSvpOUyO7UI60B3g09QliPPekipCLL5c4 XLBYWFOkr4b61/1BW/DVj6FoH/fdKsmSIj9fQNlQf915661TglB2mwUHo2Y/OYDXbldo iVhBF+KxoRKOGdfcNZcalLAVVSvyaOeQ0csUh6lXZ2JKYc1HrW/E2y5ud+MW+zqzTrjc SpIxuobyJDRvBAmRZRspG8iknG0gLM/2KX37+MF+6TeSOUSdCifV1x5Q7DYtLTbowP/q T5FnnZH2innSIyCWfCU/VIlaP7yE0YIur/5yOsgGe7njwPqji1napc0NZS2iMiA5V4br /JhA== X-Gm-Message-State: APjAAAWCx63itWiTmrBra97NbPbZ6AXPBE6mAa8bcySA6We9+ytYYO0X 0gQxurVIAo21WWdFWkzsDQokqw== X-Received: by 2002:a17:902:9a06:: with SMTP id v6mr820305plp.221.1572451703249; Wed, 30 Oct 2019 09:08:23 -0700 (PDT) Received: from cakuba.hsd1.ca.comcast.net (c-73-202-202-92.hsd1.ca.comcast.net. [73.202.202.92]) by smtp.gmail.com with ESMTPSA id f21sm267514pgh.85.2019.10.30.09.08.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Oct 2019 09:08:23 -0700 (PDT) Date: Wed, 30 Oct 2019 09:08:19 -0700 From: Jakub Kicinski To: Eric Biggers Cc: John Fastabend , Daniel Borkmann , davem@davemloft.net, glider@google.com, herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, syzbot Subject: Re: [net/tls] Re: KMSAN: uninit-value in aes_encrypt (2) Message-ID: <20191030090819.27b8c169@cakuba.hsd1.ca.comcast.net> In-Reply-To: <20191024172353.GA740@sol.localdomain> References: <00000000000065ef5f0595aafe71@google.com> <20191024172353.GA740@sol.localdomain> Organization: Netronome Systems, Ltd. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Thu, 24 Oct 2019 10:23:53 -0700, Eric Biggers wrote: > [+TLS maintainers] >=20 > This is a net/tls bug, and probably a duplicate of: >=20 > KMSAN: uninit-value in gf128mul_4k_lle (3) > https://lkml.kernel.org/linux-crypto/000000000000bf2457057b5ccda3@google= .com/T/#u > =09 > KMSAN: uninit-value in aesti_encrypt > https://lkml.kernel.org/linux-crypto/000000000000a97a15058c50c52e@google= .com/T/#u >=20 > See analysis from Alexander Potapenko here which shows that uninitialized= memory > is being passed from TLS subsystem into crypto subsystem: >=20 > https://lkml.kernel.org/linux-crypto/CAG_fn=3DUGCoDk04tL2vB981JmXgo6+-RU= PmrTa3dSsK5UbZaTjA@mail.gmail.com/ >=20 > That was a year ago, with C reproducer, and I've sent several reminders f= or this > already. What's the ETA on a fix? Or is TLS subsystem de facto unmainta= ined? Re: maintainers it may actually be that the bug is so old the people who pay attention weren't in the MAINTAINERS yet ;) That'd explain why Alexander didn't CC us. Fix posted now: net/tls: fix sk_msg trim on fallback to copy mode =F0=9F=A4=9E