From: Jann Horn <jannh@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Rik van Riel <riel@surriel.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Harry Yoo <harry.yoo@oracle.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jann Horn <jannh@google.com>
Subject: [PATCH] mm/rmap: Add anon_vma lifetime debug check
Date: Thu, 24 Jul 2025 21:13:50 +0200 [thread overview]
Message-ID: <20250724-anonvma-uaf-debug-v1-1-29989ddc4e2a@google.com> (raw)
If an anon page is mapped into userspace, its anon_vma must be alive,
otherwise rmap walks can hit UAF.
There have been syzkaller reports a few months ago[1][2] of UAF in rmap
walks that seems to indicate that there can be pages with elevated mapcount
whose anon_vma has already been freed, but I think we never figured out
what the cause is; and syzkaller only hit these UAFs when memory pressure
randomly caused reclaim to rmap-walk the affected pages, so it of course
didn't manage to create a reproducer.
Add a VM_WARN_ON_FOLIO() when we add/remove mappings of anonymous pages to
hopefully catch such issues more reliably.
Implementation note: I'm checking IS_ENABLED(CONFIG_DEBUG_VM) because,
unlike the checks above, this one would otherwise be hard to write such
that it completely compiles away in non-debug builds by itself, without
looking extremely ugly.
[1] https://lore.kernel.org/r/67abaeaf.050a0220.110943.0041.GAE@google.com
[2] https://lore.kernel.org/r/67a76f33.050a0220.3d72c.0028.GAE@google.com
Signed-off-by: Jann Horn <jannh@google.com>
---
include/linux/rmap.h | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/include/linux/rmap.h b/include/linux/rmap.h
index c4f4903b1088..ba694c436f59 100644
--- a/include/linux/rmap.h
+++ b/include/linux/rmap.h
@@ -449,6 +449,19 @@ static inline void __folio_rmap_sanity_checks(const struct folio *folio,
default:
VM_WARN_ON_ONCE(true);
}
+
+ /*
+ * Anon folios must have an associated live anon_vma as long as they're
+ * mapped into userspace.
+ * Part of the purpose of the atomic_read() is to make KASAN check that
+ * the anon_vma is still alive.
+ */
+ if (IS_ENABLED(CONFIG_DEBUG_VM) && PageAnonNotKsm(page)) {
+ unsigned long mapping = (unsigned long)folio->mapping;
+ struct anon_vma *anon_vma = (void *)(mapping - PAGE_MAPPING_ANON);
+
+ VM_WARN_ON_FOLIO(atomic_read(&anon_vma->refcount) == 0, folio);
+ }
}
/*
---
base-commit: 01a412d06bc5786eb4e44a6c8f0f4659bd4c9864
change-id: 20250724-anonvma-uaf-debug-a9db0eb4177b
--
Jann Horn <jannh@google.com>
next reply other threads:[~2025-07-24 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 19:13 Jann Horn [this message]
2025-07-24 21:52 ` Andrew Morton
2025-07-25 10:59 ` Jann Horn
2025-07-24 21:56 ` David Hildenbrand
2025-07-25 11:08 ` Jann Horn
2025-07-25 11:12 ` David Hildenbrand
2025-07-25 11:24 ` Jann Horn
2025-07-25 11:31 ` David Hildenbrand
2025-07-25 11:32 ` Lorenzo Stoakes
2025-07-25 12:00 ` Jann Horn
2025-07-25 13:48 ` Lorenzo Stoakes
2025-07-25 14:10 ` Lorenzo Stoakes
2025-07-25 14:50 ` Jann Horn
2025-07-25 14:48 ` Jann Horn
2025-07-25 15:07 ` Lorenzo Stoakes
2025-07-25 15:15 ` Jann Horn
2025-07-25 15:22 ` Lorenzo Stoakes
2025-07-25 15:27 ` Jann Horn
2025-07-25 15:58 ` Lorenzo Stoakes
2025-07-25 15:05 ` Jann Horn
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=20250724-anonvma-uaf-debug-v1-1-29989ddc4e2a@google.com \
--to=jannh@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=riel@surriel.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