From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Kairui Song <ryncsn@gmail.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
chrisl@kernel.org, Hugh Dickins <hughd@google.com>
Subject: Re: [RFC PATCH] mm/page_alloc: fix use-after-free in swap due to stale page data after split_page()
Date: Tue, 3 Feb 2026 12:14:16 +0500 [thread overview]
Message-ID: <CABXGCsO3XcXt5GDae7d74ynC6P6G2gLw3ZrwAYvSQ3PwP0mGXA@mail.gmail.com> (raw)
In-Reply-To: <CABXGCsPPeKCqj4KB3Cp0r=rWd+0KLdDZhNKkNziqCnqFu1vwag@mail.gmail.com>
On Tue, Feb 3, 2026 at 1:21 AM Mikhail Gavrilov
<mikhail.v.gavrilov@gmail.com> wrote:
>
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index 46d2008e4b99..f131494d4262 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -3859,10 +3859,11 @@ int add_swap_count_continuation(swp_entry_t
> entry, gfp_t gfp_mask)
>
> spin_lock(&si->cont_lock);
> /*
> - * Page allocation does not initialize the page's lru field,
> - * but it does always reset its private field.
> + * Page allocation does not initialize the page's lru field, and
> + * vmalloc pages from split_page() may have stale page->private.
> + * Check for SWP_CONTINUED not just non-zero.
> */
> - if (!page_private(head)) {
> + if (page_private(head) != SWP_CONTINUED) {
> BUG_ON(count & COUNT_CONTINUED);
> INIT_LIST_HEAD(&head->lru);
> set_page_private(head, SWP_CONTINUED);
>
Sorry, I sent the previous message before completing testing. The
swapfile.c fix doesn't actually work.
The problem is that stale page->private could accidentally equal
SWP_CONTINUED (32), so we can't distinguish between a legitimately
initialized page and stale data that happens to be 32. In testing, the
crash still occurred with the swapfile.c-only fix.
The correct fix is in split_page() - clear page->private for tail pages:
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index cbf758e27aa2..3604a00e2118 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3122,8 +3122,14 @@ void split_page(struct page *page, unsigned int order)
VM_BUG_ON_PAGE(PageCompound(page), page);
VM_BUG_ON_PAGE(!page_count(page), page);
- for (i = 1; i < (1 << order); i++)
+ for (i = 1; i < (1 << order); i++) {
set_page_refcounted(page + i);
+ /*
+ * Tail pages may have stale page->private from buddy
+ * allocator or previous use. Clear it.
+ */
+ set_page_private(page + i, 0);
+ }
split_page_owner(page, order, 0);
pgalloc_tag_split(page_folio(page), order, 0);
split_page_memcg(page, order);
Note: only clearing page->private, not touching page->lru (to avoid
breaking split_free_page() which may have head on a list).
Tested for 7+ hours with stress test cycling swapon/swapoff on 8GB
zram under memory pressure - no crashes.
--
Best Regards,
Mike Gavrilov.
prev parent reply other threads:[~2026-02-03 7:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 13:49 Mikhail Gavrilov
2026-01-30 13:59 ` Matthew Wilcox
2026-01-30 14:16 ` Mikhail Gavrilov
2026-01-30 15:30 ` Kairui Song
2026-01-30 15:47 ` Mikhail Gavrilov
2026-02-02 3:17 ` Kairui Song
2026-02-02 5:27 ` Mikhail Gavrilov
2026-02-02 17:54 ` Kairui Song
2026-02-02 20:21 ` Mikhail Gavrilov
2026-02-03 7:14 ` Mikhail Gavrilov [this message]
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=CABXGCsO3XcXt5GDae7d74ynC6P6G2gLw3ZrwAYvSQ3PwP0mGXA@mail.gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryncsn@gmail.com \
--cc=vbabka@suse.cz \
/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