From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Zhao Gongyi <zhaogongyi@bytedance.com>, akpm@linux-foundation.org
Cc: xu.xin@linux.dev, chengming.zhou@linux.dev, aarcange@redhat.com,
riel@redhat.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"Lorenzo Stoakes (Arm)" <ljs@kernel.org>
Subject: Re: [PATCH] mm/ksm: avoid anon_vma UAF during page merging
Date: Sun, 1 Nov 2026 19:11:25 +0100 [thread overview]
Message-ID: <79820b33-7e74-4e12-926f-1e03987d7bda@kernel.org> (raw)
In-Reply-To: <20261031182256.40205-1-zhaogongyi@bytedance.com>
On 10/31/26 19:22, Zhao Gongyi wrote:
Hi,
thanks for the report! CCing Lorenzo.
> KASAN reports a use-after-free in page_address_in_vma() while ksmd
> merges pages. ksmd keeps a folio reference across an mmap_lock drop,
> during which mremap() can remove its last mapping and free its
> anon_vma. page_address_in_vma() then dereferences the stale pointer
> from folio->mapping.
Do you have a link to the report or the actual KASAN report?
>
> KSM needs only a candidate address. write_protect_page() checks that
> the PTE maps the folio, and replace_page() verifies the saved PTE
> before replacing it. Compute the candidate from the folio index and
> VMA instead of dereferencing the folio-side anon_vma. Reject KSM
> folios because their page index is not meaningful.
>
> Fixes: 21d0d443cdc1 ("rmap: resurrect page_address_in_vma anon_vma check")
> Signed-off-by: Zhao Gongyi <zhaogongyi@bytedance.com>
> ---
> Testing:
> Unpatched mm-new: fixed-pool KSM/mremap reproduced the KASAN UAF.
> Patched mm-new: the same workload ran for 12 minutes without KASAN,
> BUG or WARNING; fork/COW KSM smoke passed.
>
> mm/ksm.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/mm/ksm.c b/mm/ksm.c
> index d6f736a..f8af5ee 100644
> --- a/mm/ksm.c
> +++ b/mm/ksm.c
> @@ -1307,7 +1307,7 @@ static int write_protect_page(struct vm_area_struct *vma, struct folio *folio,
> if (WARN_ON_ONCE(folio_test_large(folio)))
> return err;
>
> - pvmw.address = page_address_in_vma(folio, folio_page(folio, 0), vma);
> + pvmw.address = vma_anon_address(vma, folio_pgoff(folio), 1);
> if (pvmw.address == -EFAULT)
> goto out;
>
> @@ -1408,7 +1408,7 @@ static int replace_page(struct vm_area_struct *vma, struct page *page,
> int err = -EFAULT;
> struct mmu_notifier_range range;
>
> - addr = page_address_in_vma(folio, page, vma);
> + addr = vma_anon_address(vma, page_pgoff(folio, page), 1);
> if (addr == -EFAULT)
> goto out;
>
> @@ -1515,7 +1515,7 @@ static int try_to_merge_one_page(struct vm_area_struct *vma,
> if (page == kpage) /* ksm page forked */
> return 0;
>
> - if (!folio_test_anon(folio))
> + if (!folio_test_anon(folio) || folio_test_ksm(folio))
> goto out;
>
> /*
> base-commit: 243e8cdab64129d6207c398f8cf5fbb1962ff7e1
--
Cheers,
David
next prev parent reply other threads:[~2026-11-01 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 18:22 Zhao Gongyi
2026-11-01 18:11 ` David Hildenbrand (Arm) [this message]
2026-11-02 3:32 ` Zhao Gongyi
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=79820b33-7e74-4e12-926f-1e03987d7bda@kernel.org \
--to=david@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=riel@redhat.com \
--cc=xu.xin@linux.dev \
--cc=zhaogongyi@bytedance.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®