From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753186AbdJaCjo (ORCPT ); Mon, 30 Oct 2017 22:39:44 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:34093 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752063AbdJaCjm (ORCPT ); Mon, 30 Oct 2017 22:39:42 -0400 X-ME-Sender: Date: Tue, 31 Oct 2017 13:39:38 +1100 From: "Tobin C. Harding" To: Kees Cook Cc: kernel test robot , kernel-hardening@lists.openwall.com, "Jason A. Donenfeld" , "Theodore Ts'o" , Linus Torvalds , Paolo Bonzini , Tycho Andersen , "Roberts, William C" , Tejun Heo , Jordan Glover , Greg KH , Petr Mladek , Joe Perches , Ian Campbell , Sergey Senozhatsky , Catalin Marinas , Will Deacon , Steven Rostedt , Chris Fries , Dave Weinstein , Daniel Micay , Djalal Harouni , LKML , LKP Subject: Re: [lkp-robot] [printk] 7f7c60e066: BUG:KASAN:slab-out-of-bounds Message-ID: <20171031023938.GE12341@eros> References: <1508798008-1692-1-git-send-email-me@tobin.cc> <20171025162213.GH3294@yexl-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Mailer: Mutt 1.5.24 (2015-08-30) User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 30, 2017 at 05:14:59PM -0700, Kees Cook wrote: > On Wed, Oct 25, 2017 at 9:22 AM, kernel test robot > wrote: thanks for looking at this, I was at a loss as to what (if any) action I needed to take. > > FYI, we noticed the following commit (built with gcc-4.9): > > > > commit: 7f7c60e0663645e757e520245606fde9c6e326bb ("printk: hash addresses printed with %p") > > url: https://github.com/0day-ci/linux/commits/Tobin-C-Harding/printk-hash-addresses-printed-with-p/20171024-231922 > > It's not clear to me which of the various versions this test ran > against, but it seems like the printf self-tests got very confused by > the results: > > > [ 40.275423] test_printf: kvasprintf(..., "%p %p", ...) returned '3cf9adbe eff717bf', expected '0000000001234567 fffffffffedcba98' > > [ 40.296739] test_printf: vsnprintf(buf, 256, "|%-*p|%*p|", ...) returned 19, expected 39 > > [ 40.322776] test_printf: vsnprintf(buf, 16, "|%-*p|%*p|", ...) returned 19, expected 39 > > [ 40.334834] test_printf: vsnprintf(buf, 0, "|%-*p|%*p|", ...) returned 19, expected 39 > > I assume v10 will fix the width issues, but probably not the value tests... Oh, so I need to update lib/test_printf.c to cover hashed %p. > And it claims a use-after-free, too: > > > [ 39.757461] The buggy address belongs to the object at 22cb34bb > > [ 39.757461] which belongs to the cache kmalloc-32 of size 32 > > [ 39.757461] The buggy address is located 0 bytes inside of > > [ 39.757461] 32-byte region [22cb34bb, 24ac3a60) > > Which becomes rather unreadable, since the address got hashed. :P So I think we need to patch mm/kasan/report to use %pK instead of %p. I don't know what I should be doing about [ 39.757461] BUG: KASAN: slab-out-of-bounds in __test+0xee/0x13f Awesome, thanks, Tobin.