From: Mike Rapoport <rppt@kernel.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: akpm@linux-foundation.org, big-sleep-vuln-reports@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, willy@infradead.org,
david@redhat.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] mm/secretmem: fix use-after-free race in fault handler
Date: Fri, 31 Oct 2025 11:59:16 +0200 [thread overview]
Message-ID: <aQSIdCpf-2pJLwAF@kernel.org> (raw)
In-Reply-To: <20251031091818.66843-1-lance.yang@linux.dev>
On Fri, Oct 31, 2025 at 05:18:18PM +0800, Lance Yang wrote:
> From: Lance Yang <lance.yang@linux.dev>
>
> The error path in secretmem_fault() frees a folio before restoring its
> direct map status, which is a race leading to a panic.
Let's use the issue description from the report:
When a page fault occurs in a secret memory file created with
`memfd_secret(2)`, the kernel will allocate a new folio for it, mark
the underlying page as not-present in the direct map, and add it to
the file mapping.
If two tasks cause a fault in the same page concurrently, both could
end up allocating a folio and removing the page from the direct map,
but only one would succeed in adding the folio to the file
mapping. The task that failed undoes the effects of its attempt by (a)
freeing the folio again and (b) putting the page back into the direct
map. However, by doing these two operations in this order, the page
becomes available to the allocator again before it is placed back in
the direct mapping.
If another task attempts to allocate the page between (a) and (b), and
the kernel tries to access it via the direct map, it would result in a
supervisor not-present page fault.
> Fix the ordering to restore the map before the folio is freed.
... restore the direct map
With these changes
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>
> Cc: <stable@vger.kernel.org>
> Reported-by: Google Big Sleep <big-sleep-vuln-reports@google.com>
> Closes: https://lore.kernel.org/linux-mm/CAEXGt5QeDpiHTu3K9tvjUTPqo+d-=wuCNYPa+6sWKrdQJ-ATdg@mail.gmail.com/
> Signed-off-by: Lance Yang <lance.yang@linux.dev>
> ---
> mm/secretmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/secretmem.c b/mm/secretmem.c
> index c1bd9a4b663d..37f6d1097853 100644
> --- a/mm/secretmem.c
> +++ b/mm/secretmem.c
> @@ -82,13 +82,13 @@ static vm_fault_t secretmem_fault(struct vm_fault *vmf)
> __folio_mark_uptodate(folio);
> err = filemap_add_folio(mapping, folio, offset, gfp);
> if (unlikely(err)) {
> - folio_put(folio);
> /*
> * If a split of large page was required, it
> * already happened when we marked the page invalid
> * which guarantees that this call won't fail
> */
> set_direct_map_default_noflush(folio_page(folio, 0));
> + folio_put(folio);
> if (err == -EEXIST)
> goto retry;
>
> --
> 2.49.0
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-10-31 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 15:34 Oops in secretmem_fault() Big Sleep
2025-10-31 1:36 ` Andrew Morton
2025-10-31 11:48 ` Big Sleep
2025-10-31 9:18 ` [PATCH 1/1] mm/secretmem: fix use-after-free race in fault handler Lance Yang
2025-10-31 9:59 ` Mike Rapoport [this message]
2025-10-31 10:19 ` David Hildenbrand
2025-10-31 10:35 ` Lance Yang
2025-10-31 10:24 ` Lorenzo Stoakes
2025-10-31 10:34 ` Lance Yang
2025-10-31 10:34 ` Lance Yang
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=aQSIdCpf-2pJLwAF@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=big-sleep-vuln-reports@google.com \
--cc=david@redhat.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
/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