From: Michael Fara <mjfara@gmail.com>
To: senozhatsky@chromium.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, mjfara@gmail.com
Subject: [PATCH] mm/zsmalloc: fix NULL pointer dereference in get_next_zpdesc
Date: Mon, 9 Feb 2026 19:32:57 +0000 [thread overview]
Message-ID: <20260209193257.60393-1-mjfara@gmail.com> (raw)
get_next_zpdesc() calls get_zspage() which unconditionally dereferences
zpdesc->zspage without a NULL check. This causes a kernel oops when
zpdesc->zspage has been set to NULL by reset_zpdesc() during a race
between zspage destruction and page compaction/migration.
The race window is documented in a TODO comment in zs_page_migrate():
"nothing prevents a zspage from getting destroyed while it is
isolated for migration, as the page lock is temporarily dropped
after zs_page_isolate() succeeded"
The sequence is:
1. Compaction calls zs_page_isolate() on a zpdesc, then drops its
page lock.
2. Concurrently, async_free_zspage() or free_zspage() destroys the
zspage, calling reset_zpdesc() which sets zpdesc->zspage = NULL.
3. A subsequent zs_free() path calls trylock_zspage(), which iterates
zpdescs via get_next_zpdesc(). get_zspage() dereferences the now-
NULL backpointer, causing:
BUG: kernel NULL pointer dereference, address: 0000000000000000
RIP: 0010:free_zspage+0x26/0x100
Call Trace:
zs_free+0xf4/0x110
zswap_entry_free+0x7e/0x160
The migration side already has a NULL guard (zs_page_migrate line 1675:
"if (!zpdesc->zspage) return 0;"), but get_next_zpdesc() lacks the same
protection.
Fix this by reading zpdesc->zspage directly in get_next_zpdesc()
instead of going through get_zspage(), and returning NULL when the
backpointer is NULL. This stops iteration safely — the caller treats
it as the end of the page chain.
Signed-off-by: Michael Fara <mjfara@gmail.com>
---
mm/zsmalloc.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -735,7 +735,19 @@ static struct zspage *get_zspage(struct zpdesc *zpdesc)
static struct zpdesc *get_next_zpdesc(struct zpdesc *zpdesc)
{
- struct zspage *zspage = get_zspage(zpdesc);
+ struct zspage *zspage = zpdesc->zspage;
+
+ /*
+ * If the backpointer is NULL, this zpdesc was already freed via
+ * reset_zpdesc() by a racing async_free_zspage() while isolated
+ * for compaction. See the TODO comment in zs_page_migrate().
+ */
+ if (unlikely(!zspage)) {
+ WARN_ON_ONCE(1);
+ return NULL;
+ }
+
+ BUG_ON(zspage->magic != ZSPAGE_MAGIC);
if (unlikely(ZsHugePage(zspage)))
return NULL;
--
2.39.0
next reply other threads:[~2026-02-09 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 19:32 Michael Fara [this message]
2026-02-09 22:50 ` Joshua Hahn
2026-02-09 23:16 ` Joshua Hahn
2026-02-18 5:56 ` Sergey Senozhatsky
2026-02-09 19:36 Michael Fara
2026-02-09 19:37 Michael Fara
2026-02-18 5:01 ` Sergey Senozhatsky
2026-02-18 5:46 ` Sergey Senozhatsky
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=20260209193257.60393-1-mjfara@gmail.com \
--to=mjfara@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=senozhatsky@chromium.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