From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Vernon Yang <vernon2gm@gmail.com>
Cc: akpm@linux-foundation.org, ljs@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 2/3] mm: khugepaged: fix folio is used after pte_unmap_unlock()
Date: Wed, 26 Aug 2026 09:58:01 +0200 [thread overview]
Message-ID: <d057f5f3-e2e1-42b3-bbbe-c3ae61764887@kernel.org> (raw)
In-Reply-To: <f285e26a-b790-4afb-91e9-a2b404df018f@gmail.com>
On 8/26/26 04:46, Vernon Yang wrote:
> On Mon, Aug 24, 2026 at 01:57:15PM +0200, David Hildenbrand (Arm) wrote:
>> On 8/24/26 11:29, Vernon Yang wrote:
>>> From: Vernon Yang <yanglincheng@kylinos.cn>
>>>
>>> After the page table lock has dropped, the folio can be freed
>>> concurrently. The trace_mm_khugepaged_scan_pmd() is left with
>>> a dangling folio pointer.
>>>
>>> So using the folio_pfn() before dropping the page table lock,
>>> closing use-after-free window.
>>>
>>> Fixes: 7d2eba0557c1 ("mm: add tracepoint for scanning pages")
>>> 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 7b526528f85b..fa828967e1fb 100644
>>> --- a/include/trace/events/huge_memory.h
>>> +++ b/include/trace/events/huge_memory.h
>>> @@ -55,10 +55,10 @@ SCAN_STATUS
>>>
>>> TRACE_EVENT(mm_khugepaged_scan_pmd,
>>>
>>> - TP_PROTO(struct mm_struct *mm, struct folio *folio,
>>> + TP_PROTO(struct mm_struct *mm, unsigned long pfn,
>>> int referenced, int none_or_zero, int status, int unmapped),
>>>
>>> - TP_ARGS(mm, folio, referenced, none_or_zero, status, unmapped),
>>> + TP_ARGS(mm, pfn, referenced, none_or_zero, status, unmapped),
>>>
>>> TP_STRUCT__entry(
>>> __field(struct mm_struct *, mm)
>>> @@ -71,7 +71,7 @@ TRACE_EVENT(mm_khugepaged_scan_pmd,
>>>
>>> TP_fast_assign(
>>> __entry->mm = mm;
>>> - __entry->pfn = folio ? folio_pfn(folio) : -1;
>>> + __entry->pfn = pfn;
>>> __entry->referenced = referenced;
>>> __entry->none_or_zero = none_or_zero;
>>> __entry->status = status;
>>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>>> index 00337405c0e0..4e0fca5942dd 100644
>>> --- a/mm/khugepaged.c
>>> +++ b/mm/khugepaged.c
>>> @@ -1618,6 +1618,7 @@ static enum scan_result collapse_scan_pmd(struct mm_struct *mm,
>>> enum scan_result result = SCAN_FAIL;
>>> struct page *page = NULL;
>>> struct folio *folio = NULL;
>>> + unsigned long pfn = -1;
>>> unsigned long addr;
>>> unsigned long enabled_orders;
>>> spinlock_t *ptl;
>>> @@ -1780,6 +1781,8 @@ static enum scan_result collapse_scan_pmd(struct mm_struct *mm,
>>> result = SCAN_SUCCEED;
>>> }
>>> out_unmap:
>>> + if (folio)
>>> + pfn = folio_pfn(folio);
>>
>> Should we reset the folio to NULL at the beginning of the loop? Then we really
>> only trace the PFN if it really was problematic.
>
> Yes, this is a pre-existing bug, and I'll fix it together. Thanks!
>
> But it is not at the beginning of the loop, it is at the __ending__ of
> the loop, for the same reason as PATCH#1.
See my reply to patch #1, hth.
--
Cheers,
David
next prev parent reply other threads:[~2026-08-26 7:58 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) [this message]
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)
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=d057f5f3-e2e1-42b3-bbbe-c3ae61764887@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.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