From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.zx2c4.com (lists.zx2c4.com [165.227.139.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id EBF43C77B7A for ; Wed, 24 May 2023 15:46:22 +0000 (UTC) Received: by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 7395f820; Wed, 24 May 2023 15:39:40 +0000 (UTC) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lists.zx2c4.com (ZX2C4 Mail Server) with ESMTPS id 4e309c22 (TLSv1.2:ECDHE-ECDSA-AES256-GCM-SHA384:256:NO) for ; Wed, 24 May 2023 15:39:39 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B064663E6C; Wed, 24 May 2023 15:39:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A60B2C433D2; Wed, 24 May 2023 15:39:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684942777; bh=9Hl32z8O29zupLewPwrp8TBa3k0iI9CyhI88kKC9mx0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=LeXRm7BtiZTlebT681eMU23sdH7H3sx167YpHnt5zUzTXsy44X1JAfbDnIrBJ03rn 19Xpt0L3QVP5WH7cZyizBHJJIS/nDyh3pgzmRvR5iSIKpowHGWtlhTYYz6jWduPvsx /kU8JlHTQXC5B/QbvoP6Dbw73YwFfbqMaUVmUmX8oem0zwojl2enIcZFazIW3vXYca jgbWY4A0mTTsmC9CtMNsO2ctPty55mAQu6OLhG2RABV1LavDUqbFCXCZBzrnvKl53U gtEgxaLeayUCj1TrpE8ckP9p8gmbT5XElDKW2lo/J8KhX4cmJDWMv+UGx92Lrisixv 93vgt0zerCxmQ== Date: Wed, 24 May 2023 08:39:35 -0700 From: Jakub Kicinski To: Dmitry Vyukov Cc: Eric Dumazet , "Jason A. Donenfeld" , syzbot , netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, davem@davemloft.net, linux-kernel@vger.kernel.org, pabeni@redhat.com, wireguard@lists.zx2c4.com, jann@thejh.net Subject: Re: [syzbot] [wireguard?] KASAN: slab-use-after-free Write in enqueue_timer Message-ID: <20230524083935.7108f17f@kernel.org> In-Reply-To: <20230524083341.0cd435f7@kernel.org> References: <000000000000c0b11d05fa917fe3@google.com> <20230523090512.19ca60b6@kernel.org> <20230523094108.0c624d47@kernel.org> <20230523094736.3a9f6f8c@kernel.org> <20230524083341.0cd435f7@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.30rc1 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" On Wed, 24 May 2023 08:33:41 -0700 Jakub Kicinski wrote: > On Wed, 24 May 2023 10:24:31 +0200 Dmitry Vyukov wrote: > > FWIW There are more report examples on the dashboard. > > There are some that don't mention wireguard nor usbnet, e.g.: > > https://syzkaller.appspot.com/text?tag=CrashReport&x=17dd2446280000 > > So that's probably red herring. But they all seem to mention alloc_netdev_mqs. > > While we have you, let me ask about the possibility of having vmcore > access - I think it'd be very useful to solve this mystery. > With a bit of luck the timer still has the function set. I take that back. Memory state around the buggy address: ffff88801ecc1400: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88801ecc1480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff88801ecc1500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff88801ecc1580: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff88801ecc1600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb