From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9A3EF20FA96; Wed, 22 Jan 2025 12:36:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737549395; cv=none; b=dn39usHiOfOyYAbVXUe/kmNvgerkM5vTmb63zco2ySFv7PX3HdCxyrQLBNoCfpFRvuOBJOjnwIkerZBhU3CnMcC5xm+fdl8ZbfbFyJ5EhkOeqIA3PPmkqqdqSs9k82atNE/ZMkR/7nbY9Kji41swUEizhz+LfiSTxmH5w/e28B0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737549395; c=relaxed/simple; bh=9gDpYQf+1EFcjOBEg/Y8DM/1zRuZ6A/kYEvt5QghAaU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=G9ph0P9+P6tOpffJ1zySXgxAcXB2rVUuZfsi/sl5DrNbS/n0kmojXYRLZSpgK+LkfOitY013zPbtsnacvvAo5m/1boV11ESx98iTwZIEM82792jgrsyz0u8dg3XNwz9J+p7cH3eabyxaLws2HY3c8YmN+KinqC5r4TMjsUNbDmo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=YuZ+ingJ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="YuZ+ingJ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BBE8DC4CED6; Wed, 22 Jan 2025 12:36:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1737549395; bh=9gDpYQf+1EFcjOBEg/Y8DM/1zRuZ6A/kYEvt5QghAaU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=YuZ+ingJJIN8znbT3pwD8zNYjVleg2s9TZeThf/34oKNjK+u2VSSzsx94LAbe4veu 4mKkN+rqdrrT4EUI8IdJAHp+TgJ9gyefjW1fBr+U0zlJV5TUWTA39pzYtNxhSNywNH L7XgEpqsOMBFZibMzdDD/dFX/2IJ8Pu3jOeAcf+M= Date: Wed, 22 Jan 2025 13:36:32 +0100 From: Greg KH To: Lorenzo Stoakes Cc: cve@kernel.org, linux-kernel@vger.kernel.org, linux-cve-announce@vger.kernel.org Subject: Re: CVE-2024-57937: mm: reinstate ability to map write-sealed memfd mappings read-only Message-ID: <2025012228-tarot-garland-80c1@gregkh> References: <9bf44136-e6a5-4275-b7ea-5022c3cfd543@lucifer.local> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9bf44136-e6a5-4275-b7ea-5022c3cfd543@lucifer.local> On Wed, Jan 22, 2025 at 11:51:10AM +0000, Lorenzo Stoakes wrote: > On Sun, Sep 16, 2001 at 11:00:00PM +0000, Greg Kroah-Hartman wrote: > > Description > > =========== > > > > In the Linux kernel, the following vulnerability has been resolved: > > > > mm: reinstate ability to map write-sealed memfd mappings read-only > > Hi Greg, > > This is not a vulnerability and I don't see how it could possibly be > exploited. So unless somebody can suggest a means by which it could be, I > suggest this CVE should be dropped. > > Thanks, Lorenzo > > > > > Patch series "mm: reinstate ability to map write-sealed memfd mappings > > read-only". > > > > In commit 158978945f31 ("mm: perform the mapping_map_writable() check > > after call_mmap()") (and preceding changes in the same series) it became > > possible to mmap() F_SEAL_WRITE sealed memfd mappings read-only. I thought the ability to mmap a sealed memfd mapping as read-only that didn't want to be mmaped that way was a "vulnerability fix". If you don't think so, then that's fine, we'll be glad to revoke this, just let us know. thanks, greg k-h