From: "David Hildenbrand (Arm)" <david@kernel.org>
To: n3rd <18670333770@163.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"ziy@nvidia.com" <ziy@nvidia.com>,
"ljs@kernel.org" <ljs@kernel.org>,
"kas@kernel.org" <kas@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
"peterx@redhat.com" <peterx@redhat.com>,
"security@kernel.org" <security@kernel.org>
Subject: Re: [SECURITY] mm: split file arm of unmap_folio() drops RWP PTE state
Date: Tue, 10 Nov 2026 12:51:40 +0100 [thread overview]
Message-ID: <895188b0-b79b-49c0-aba8-c04cb3292e10@kernel.org> (raw)
In-Reply-To: <3f250fc2.bbe22.1a1c5441381.Coremail.18670333770@163.com>
On 11/10/26 12:42, n3rd wrote:
>
> Hello,
>
> I am reporting a security bug in the Linux kernel.
>
> 1. Affected kernel versions
> Linux v7.3-rc7 (mainline, built and tested as 7.3.0-rc7) is affected and was
> reproduced on two fresh boots. v7.3-rc6 carries the same code and is affected as
> well. v7.2.9 does not have the RWP feature at all, because UFFDIO_RWPROTECT,
> UFFD_FEATURE_RWP and VM_UFFD_RWP were added in v7.3, so it is not affected.
> Triggering additionally requires CONFIG_TRANSPARENT_HUGEPAGE for the PTE mapped
> shmem big folio and CONFIG_USERFAULTFD_RWP. There is no upstream fix as of v7.3-
> rc7 and no CVE has been assigned.
Please don't indicate uffd problems where we lose a pte bit as a security
problem. It's not.
--
Cheers,
David
parent reply other threads:[~2026-11-10 11:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3f250fc2.bbe22.1a1c5441381.Coremail.18670333770@163.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=895188b0-b79b-49c0-aba8-c04cb3292e10@kernel.org \
--to=david@kernel.org \
--cc=18670333770@163.com \
--cc=akpm@linux-foundation.org \
--cc=kas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=security@kernel.org \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®