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 X-Spam-Level: X-Spam-Status: No, score=-5.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 76374C43612 for ; Fri, 4 Jan 2019 09:38:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3BA7B217F5 for ; Fri, 4 Jan 2019 09:38:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1546594692; bh=QLhTYGQwMwtVRseZ3bhZbf/199ZxOYmCtTosGZ8C4kU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=wkcyNE90C7srIRfDZBCaU8tIl5pwhlYIXd4FfsKjphJ0jUGLMdTnIqM0cWZDW7g// bR+Hj6okvKvpNk9UVQEQU+DSPOzsvMpbo2GHVLfPP7lVqdLPQc4WSqoeWh1Yh4jN49 A4FzjNFysW5e3Ybrbd0L6YTUyDZLmktGz1XXqaVg= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727669AbfADJiL (ORCPT ); Fri, 4 Jan 2019 04:38:11 -0500 Received: from mx2.suse.de ([195.135.220.15]:38998 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725958AbfADJiL (ORCPT ); Fri, 4 Jan 2019 04:38:11 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id C06B6AC81; Fri, 4 Jan 2019 09:38:09 +0000 (UTC) Date: Fri, 4 Jan 2019 10:38:08 +0100 From: Michal Hocko To: Roman Penyaev Cc: Andrew Morton , Andrey Ryabinin , Joe Perches , "Luis R. Rodriguez" , linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH 1/3] mm/vmalloc: fix size check for remap_vmalloc_range_partial() Message-ID: <20190104093808.GJ31793@dhcp22.suse.cz> References: <20190103145954.16942-1-rpenyaev@suse.de> <20190103145954.16942-2-rpenyaev@suse.de> <20190103151357.GR31793@dhcp22.suse.cz> <20190103194054.GB31793@dhcp22.suse.cz> <5502b64d6c508f5432386d2cfe999844@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5502b64d6c508f5432386d2cfe999844@suse.de> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 03-01-19 21:31:58, Roman Penyaev wrote: > On 2019-01-03 20:40, Michal Hocko wrote: > > On Thu 03-01-19 20:27:26, Roman Penyaev wrote: > > > On 2019-01-03 16:13, Michal Hocko wrote: > > > > On Thu 03-01-19 15:59:52, Roman Penyaev wrote: > > > > > area->size can include adjacent guard page but get_vm_area_size() > > > > > returns actual size of the area. > > > > > > > > > > This fixes possible kernel crash when userspace tries to map area > > > > > on 1 page bigger: size check passes but the following > > > > > vmalloc_to_page() > > > > > returns NULL on last guard (non-existing) page. > > > > > > > > Can this actually happen? I am not really familiar with all the callers > > > > of this API but VM_NO_GUARD is not really used wildly in the kernel. > > > > > > Exactly, by default (VM_NO_GUARD is not set) each area has guard page, > > > thus the area->size will be bigger. The bug is not reproduced if > > > VM_NO_GUARD is set. > > > > > > > All I can see is kasan na arm64 which doesn't really seem to use it > > > > for vmalloc. > > > > > > > > So is the problem real or this is a mere cleanup? > > > > > > This is the real problem, try this hunk for any file descriptor which > > > provides > > > mapping, or say modify epoll as example: > > > > OK, my response was more confusing than I intended. I meant to say. Is > > there any in kernel code that would allow the bug have had in mind? > > In other words can userspace trick any existing code? > > In theory any existing caller of remap_vmalloc_range() which does > not have an explicit size check should trigger an oops, e.g. this is > a good candidate: > > *** drivers/media/usb/stkwebcam/stk-webcam.c: > v4l_stk_mmap[789] ret = remap_vmalloc_range(vma, sbuf->buffer, > 0); Hmm, sbuf->buffer is allocated in stk_setup_siobuf to have buf->v4lbuf.length. mmap callback maps this buffer to the vma size and that is indeed not enforced to be <= length AFAICS. So you are right! Can we have an example in the changelog please? Thanks! -- Michal Hocko SUSE Labs