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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1576DC433F5 for ; Fri, 25 Feb 2022 04:19:05 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5343B8D0002; Thu, 24 Feb 2022 23:19:05 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 4E1B68D0001; Thu, 24 Feb 2022 23:19:05 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3D0328D0002; Thu, 24 Feb 2022 23:19:05 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0078.hostedemail.com [216.40.44.78]) by kanga.kvack.org (Postfix) with ESMTP id 2AE048D0001 for ; Thu, 24 Feb 2022 23:19:05 -0500 (EST) Received: from smtpin18.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id DEC8B181327BC for ; Fri, 25 Feb 2022 04:19:04 +0000 (UTC) X-FDA: 79179997008.18.40E5425 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf24.hostedemail.com (Postfix) with ESMTP id 4F041180002 for ; Fri, 25 Feb 2022 04:19:04 +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 ams.source.kernel.org (Postfix) with ESMTPS id 75565B82B06; Fri, 25 Feb 2022 04:19:02 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 25B7CC340E7; Fri, 25 Feb 2022 04:19:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1645762741; bh=hzQG2QIF47CHmg+UgPl9geBa5xc95GKwwMRDXpJTRUc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=GH/0Q5c1WEvwOQfXb55HDbDlUkrSc/I163Nnq0aFQTQJfBdXicD6kqNr9J79iSbLJ IgekHROK/Jje0DdSdZo8rNge06yDWNXEpwZwnWyZjxHVJRlqKyFBRWSIgmXjh1AS7C CdIWgGRahwNaBpZwI7wPDst4qNIXY2xccdiAjYR0= Date: Thu, 24 Feb 2022 20:18:59 -0800 From: Andrew Morton To: Suren Baghdasaryan Cc: mhocko@kernel.org, mhocko@suse.com, shy828301@gmail.com, rientjes@google.com, willy@infradead.org, hannes@cmpxchg.org, guro@fb.com, riel@surriel.com, minchan@kernel.org, kirill@shutemov.name, aarcange@redhat.com, brauner@kernel.org, christian@brauner.io, hch@infradead.org, oleg@redhat.com, david@redhat.com, jannh@google.com, shakeelb@google.com, luto@kernel.org, christian.brauner@ubuntu.com, fweimer@redhat.com, jengelh@inai.de, timmurray@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-team@android.com, syzbot+2ccf63a4bd07cf39cab0@syzkaller.appspotmail.com, Liam Howlett , Matthew Wilcox Subject: Re: [PATCH 1/1] mm: fix use-after-free bug when mm->mmap is reused after being freed Message-Id: <20220224201859.a38299b6c9d52cb51e6738ea@linux-foundation.org> In-Reply-To: <20220215201922.1908156-1-surenb@google.com> References: <20220215201922.1908156-1-surenb@google.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 4F041180002 X-Rspam-User: Authentication-Results: imf24.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b="GH/0Q5c1"; spf=pass (imf24.hostedemail.com: domain of akpm@linux-foundation.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-Stat-Signature: fk5zei3n744tr4uiqpawd19zoqgtbngu X-HE-Tag: 1645762744-748572 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, 15 Feb 2022 12:19:22 -0800 Suren Baghdasaryan wrote: > After exit_mmap frees all vmas in the mm, mm->mmap needs to be reset, > otherwise it points to a vma that was freed and when reused leads to > a use-after-free bug. > > ... > > --- a/mm/mmap.c > +++ b/mm/mmap.c > @@ -3186,6 +3186,7 @@ void exit_mmap(struct mm_struct *mm) > vma = remove_vma(vma); > cond_resched(); > } > + mm->mmap = NULL; > mmap_write_unlock(mm); > vm_unacct_memory(nr_accounted); > } After the Maple tree patches, mm_struct.mmap doesn't exist. So I'll revert this fix as part of merging the maple-tree parts of linux-next. I'll be sending this fix to Linus this week. All of which means that the thusly-resolved Maple tree patches might reintroduce this use-after-free bug.