Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp843230pxb; Thu, 17 Feb 2022 16:21:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJzitJ0IKDmXeply63ipkU1kYudZhzBMfrLCICFvOdwhNAsJn0VZ6fbsGAKwpkC5Y4g+Fxjj X-Received: by 2002:a05:6a00:21c6:b0:49f:dcb7:2bf2 with SMTP id t6-20020a056a0021c600b0049fdcb72bf2mr5253049pfj.19.1645143705386; Thu, 17 Feb 2022 16:21:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645143705; cv=none; d=google.com; s=arc-20160816; b=Lkm/6OEhbuXPbX3VCT/yECv0G0DTcyD5UCo2vSJtk+evx0R9hYhi4qGyS6dwzL6tOa UZ2IR5/Iqxe08M4l2CjV4yuCHZhHO+m9ff+A6RVp5WwIL3hvSm5Xf35JCsb51abVbNF2 f/1FMimAMJaKxuOiY228LvtPIxXjLiapMYDfhua5M1P0kYamsvr9liUK0o1v3yOhcADU kj+nNpRwTEi94R0+vM4HVDzO0BvUzKwZ0QPRSMoR+Ta+qxFzBA9awbW8g+hdzE8OHg6a 0qaec989xh/TSO3Uxj4o4ZinjG8xfk1bsHXW/6/cjned2mNxRet5oAq2Tsu8Sa7oI5DU SWXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=BGPe972J3ZYovg4J/REQe4HRT89OCoap+z3zIy+ad4Y=; b=D9aPO5WcoAtr/jYGSmCCkAbw0qZh4FVa2gkebftXpGpwgf/6gl8EUQy6Z4T/EXK759 NCNGiJRGFcXvfVg1/2RwedZ4DUPdejlpyDIFUN+GQBcOY3zYXfXzy9+fumcnOkI0rjsD xZSnaXefBFr8PkqP+Pc7fXYtqmSLdle7qFo0mRWJlGH7mJTPUnVyj5CScJLJ+lQhiq7x NTeCkeXDL5PouhMfS/yJbZtuesPLBkSSTtIyQfzc3XHcvi+7nRFCzXbuOwe36aLKaWIx SXTo//h+heo3yCnMtQcbJGZ2eoZV/aTMwjaKH7iv5JgN7s71rUmozKEyr1SLw1DzFKYl P/rA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=korg header.b=CGhuRuGZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id j184si9645444pge.630.2022.02.17.16.21.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 17 Feb 2022 16:21:45 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@linux-foundation.org header.s=korg header.b=CGhuRuGZ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 491612F7146; Thu, 17 Feb 2022 15:44:24 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243331AbiBQUvQ (ORCPT + 99 others); Thu, 17 Feb 2022 15:51:16 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:53942 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231586AbiBQUvP (ORCPT ); Thu, 17 Feb 2022 15:51:15 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A083163D75 for ; Thu, 17 Feb 2022 12:51:00 -0800 (PST) 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 076BDB81B0E for ; Thu, 17 Feb 2022 20:50:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D19DFC340E8; Thu, 17 Feb 2022 20:50:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1645131057; bh=M3DCGGewZr70eOjOG2Q+HAYxvOudSciSqV1kblBNK10=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=CGhuRuGZUgReF4FrJXds7xwuu7lZPVgEWg6FkVnzGeppquRnxl8H1BlU/gNxN5YhW 0R/EB451JzKtQlDEOcOa1lQyMr2VqCnuo8J+uq64RhvnpYkTxur4uAanC15/ruRL+G PLoADDOvAC4+tSBvui4R4PEP+ncpLCTe41J82m1I= Date: Thu, 17 Feb 2022 12:50:56 -0800 From: Andrew Morton To: Suren Baghdasaryan Cc: Michal Hocko , 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 Subject: Re: [PATCH 1/1] mm: fix use-after-free bug when mm->mmap is reused after being freed Message-Id: <20220217125056.df4073b42f2d911c99939e93@linux-foundation.org> In-Reply-To: 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-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 Feb 2022 11:51:13 -0800 Suren Baghdasaryan wrote: > This changelog is very detailed and I support switching to it. Andrew, > please let me know if I should re-post the patch with this description > or you will just amend the one in your tree. I have made that change. From: Suren Baghdasaryan Subject: mm: fix use-after-free bug when mm->mmap is reused after being freed oom reaping (__oom_reap_task_mm) relies on a 2 way synchronization with exit_mmap. First it relies on the mmap_lock to exclude from unlock path[1], page tables tear down (free_pgtables) and vma destruction. This alone is not sufficient because mm->mmap is never reset. For historical reasons[2] the lock is taken there is also MMF_OOM_SKIP set for oom victims before. The oom reaper only ever looks at oom victims so the whole scheme works properly but process_mrelease can opearate on any task (with fatal signals pending) which doesn't really imply oom victims. That means that the MMF_OOM_SKIP part of the synchronization doesn't work and it can see a task after the whole address space has been demolished and traverse an already released mm->mmap list. This leads to use after free as properly caught up by KASAN report. Fix the issue by reseting mm->mmap so that MMF_OOM_SKIP synchronization is not needed anymore. The MMF_OOM_SKIP is not removed from exit_mmap yet but it acts mostly as an optimization now. [1] 27ae357fa82b ("mm, oom: fix concurrent munlock and oom reaper unmap, v3") [2] 212925802454 ("mm: oom: let oom_reap_task and exit_mmap run concurrently") [mhocko@suse.com: changelog rewrite] Link: https://lore.kernel.org/all/00000000000072ef2c05d7f81950@google.com/ Link: https://lkml.kernel.org/r/20220215201922.1908156-1-surenb@google.com Fixes: 64591e8605d6 ("mm: protect free_pgtables with mmap_lock write lock in exit_mmap") Signed-off-by: Suren Baghdasaryan Reported-by: syzbot+2ccf63a4bd07cf39cab0@syzkaller.appspotmail.com Suggested-by: Michal Hocko Reviewed-by: Rik van Riel Reviewed-by: Yang Shi Acked-by: Michal Hocko Cc: David Rientjes Cc: Matthew Wilcox Cc: Johannes Weiner Cc: Roman Gushchin Cc: Rik van Riel Cc: Minchan Kim Cc: Kirill A. Shutemov Cc: Andrea Arcangeli Cc: Christian Brauner Cc: Christoph Hellwig Cc: Oleg Nesterov Cc: David Hildenbrand Cc: Jann Horn Cc: Shakeel Butt Cc: Andy Lutomirski Cc: Christian Brauner Cc: Florian Weimer Cc: Jan Engelhardt Cc: Tim Murray Signed-off-by: Andrew Morton --- mm/mmap.c | 1 + 1 file changed, 1 insertion(+) --- a/mm/mmap.c~mm-fix-use-after-free-bug-when-mm-mmap-is-reused-after-being-freed +++ a/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); } _