From: Stephan Mueller Subject: Re: x509 parsing bug + fuzzing crypto in the userspace Date: Thu, 23 Nov 2017 13:35:33 +0100 Message-ID: <3132962.8EQ63lqCxc@tauon.chronox.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Eric Biggers , Alexander Potapenko , linux-crypto@vger.kernel.org, Kostya Serebryany , keyrings@vger.kernel.org, Andrey Konovalov To: Dmitry Vyukov Return-path: Received: from mail.eperm.de ([89.247.134.16]:42420 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751968AbdKWMff (ORCPT ); Thu, 23 Nov 2017 07:35:35 -0500 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: Am Donnerstag, 23. November 2017, 12:34:54 CET schrieb Dmitry Vyukov: Hi Dmitry, > Btw, I've started doing some minimal improvements, did not yet sorted > out alg types/names, and fuzzer started scratching surface: > > WARNING: kernel stack regs has bad 'bp' value 77 Nov 23 2017 12:29:36 CET > general protection fault in af_alg_free_areq_sgls 54 Nov 23 2017 12:23:30 > CET general protection fault in crypto_chacha20_crypt 100 Nov 23 2017 > 12:29:48 CET suspicious RCU usage at ./include/trace/events/kmem.h:LINE 88 > Nov 23 2017 12:29:15 CET This all looks strange. Where would RCU come into play with af_alg_free_areq_sgls? Do you have a reproducer? > > This strongly suggests that we need to dig deeper. Absolutely. That is why I started my fuzzer that turned up already quite some issues. > -- > To unsubscribe from this list: send the line "unsubscribe keyrings" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html Ciao Stephan