From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Vernon Yang <vernon2gm@gmail.com>
Cc: akpm@linux-foundation.org, david@kernel.org,
nico.pache@linux.dev, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, usama.arif@linux.dev,
zokeefe@google.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, stable@vger.kernel.org,
Vernon Yang <yanglincheng@kylinos.cn>
Subject: Re: [PATCH v3 3/3] mm: khugepaged: fix folio is used after folio_put/unlock()
Date: Wed, 26 Aug 2026 09:09:16 +0100 [thread overview]
Message-ID: <ao6e9RxwQ-KC1Ikq@gremlin> (raw)
In-Reply-To: <20260824092935.73892-4-vernon2gm@gmail.com>
On Mon, Aug 24, 2026 at 05:29:35PM +0800, Vernon Yang wrote:
> From: Vernon Yang <yanglincheng@kylinos.cn>
>
> On the rollback path, folio_put() has already dropped the last reference
> of new_folio. On the success path, new_folio is already unlocked and can
> be freed concurrently. The trace_mm_khugepaged_collapse_file() is left
> with a dangling folio pointer.
>
> So using the folio_pfn() before dropping the reference, closing
> use-after-free window.
>
> Fixes: 4c9473e87e75 ("mm/khugepaged: add tracepoint to collapse_file()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Vernon Yang <yanglincheng@kylinos.cn>
> ---
> include/trace/events/huge_memory.h | 6 +++---
> mm/khugepaged.c | 5 ++++-
> 2 files changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/include/trace/events/huge_memory.h b/include/trace/events/huge_memory.h
> index fa828967e1fb..5fb4d92cfd84 100644
> --- a/include/trace/events/huge_memory.h
> +++ b/include/trace/events/huge_memory.h
> @@ -211,10 +211,10 @@ TRACE_EVENT(mm_khugepaged_scan_file,
> );
>
> TRACE_EVENT(mm_khugepaged_collapse_file,
> - TP_PROTO(struct mm_struct *mm, struct folio *new_folio, pgoff_t index,
> + TP_PROTO(struct mm_struct *mm, unsigned long new_pfn, pgoff_t index,
> unsigned long addr, bool is_shmem, struct file *file,
> int nr, int result),
> - TP_ARGS(mm, new_folio, index, addr, is_shmem, file, nr, result),
> + TP_ARGS(mm, new_pfn, index, addr, is_shmem, file, nr, result),
> TP_STRUCT__entry(
> __field(struct mm_struct *, mm)
> __field(unsigned long, hpfn)
> @@ -228,7 +228,7 @@ TRACE_EVENT(mm_khugepaged_collapse_file,
>
> TP_fast_assign(
> __entry->mm = mm;
> - __entry->hpfn = new_folio ? folio_pfn(new_folio) : -1;
> + __entry->hpfn = new_pfn;
> __entry->index = index;
> __entry->addr = addr;
> __entry->is_shmem = is_shmem;
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index 4e0fca5942dd..24347f1a94ae 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -2254,6 +2254,7 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
> struct address_space *mapping = file->f_mapping;
> struct page *dst;
> struct folio *folio, *tmp, *new_folio;
> + unsigned long new_pfn = -1;
Nitty but:
Could we use pfn_t? I don't love that we are inconsistent with that.
Also the general pattern for pfn names is pfn_xxx so pfn_new instead?
> pgoff_t index = 0, end = start + HPAGE_PMD_NR;
> LIST_HEAD(pagelist);
> XA_STATE_ORDER(xas, &mapping->i_pages, start, HPAGE_PMD_ORDER);
> @@ -2633,6 +2634,7 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
> retract_page_tables(mapping, start);
> if (cc && !cc->is_khugepaged)
> result = SCAN_PTE_MAPPED_HUGEPAGE;
> + new_pfn = folio_pfn(new_folio);
> folio_unlock(new_folio);
>
> /*
> @@ -2671,12 +2673,13 @@ static enum scan_result collapse_file(struct mm_struct *mm, unsigned long addr,
> }
>
> new_folio->mapping = NULL;
> + new_pfn = folio_pfn(new_folio);
>
> folio_unlock(new_folio);
> folio_put(new_folio);
> out:
> VM_BUG_ON(!list_empty(&pagelist));
> - trace_mm_khugepaged_collapse_file(mm, new_folio, index, addr, is_shmem, file, HPAGE_PMD_NR, result);
> + trace_mm_khugepaged_collapse_file(mm, new_pfn, index, addr, is_shmem, file, HPAGE_PMD_NR, result);
> return result;
> }
>
> --
> 2.53.0
>
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-08-26 8:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 9:29 [PATCH v3 0/3] mm: khugepaged: fix tracepoint UAF Vernon Yang
2026-08-24 9:29 ` [PATCH v3 1/3] mm: khugepaged: fix swap entry value to folio_pfn() Vernon Yang
2026-08-24 11:54 ` David Hildenbrand (Arm)
2026-08-26 2:44 ` Vernon Yang
2026-08-26 7:57 ` David Hildenbrand (Arm)
2026-08-26 8:07 ` Lorenzo Stoakes (ARM)
2026-08-26 8:08 ` David Hildenbrand (Arm)
2026-08-26 8:11 ` Lorenzo Stoakes (ARM)
2026-08-26 8:16 ` David Hildenbrand (Arm)
2026-08-26 8:24 ` David Hildenbrand (Arm)
2026-08-26 8:35 ` Lorenzo Stoakes (ARM)
2026-08-26 9:10 ` David Hildenbrand (Arm)
2026-08-26 9:21 ` Vernon Yang
2026-08-26 11:04 ` Lorenzo Stoakes (ARM)
2026-08-26 9:08 ` Vernon Yang
2026-08-24 9:29 ` [PATCH v3 2/3] mm: khugepaged: fix folio is used after pte_unmap_unlock() Vernon Yang
2026-08-24 11:57 ` David Hildenbrand (Arm)
2026-08-26 2:46 ` Vernon Yang
2026-08-26 7:58 ` David Hildenbrand (Arm)
2026-08-26 8:12 ` Lorenzo Stoakes (ARM)
2026-08-26 8:42 ` Lorenzo Stoakes (ARM)
2026-08-24 9:29 ` [PATCH v3 3/3] mm: khugepaged: fix folio is used after folio_put/unlock() Vernon Yang
2026-08-24 11:59 ` David Hildenbrand (Arm)
2026-08-26 2:47 ` Vernon Yang
2026-08-26 8:09 ` Lorenzo Stoakes (ARM) [this message]
2026-08-26 8:14 ` David Hildenbrand (Arm)
2026-08-26 8:23 ` Lorenzo Stoakes (ARM)
2026-08-26 8:41 ` Lorenzo Stoakes (ARM)
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=ao6e9RxwQ-KC1Ikq@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nico.pache@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=usama.arif@linux.dev \
--cc=vernon2gm@gmail.com \
--cc=yanglincheng@kylinos.cn \
--cc=zokeefe@google.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