summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorRuipeng Qi <ruipengqi3@gmail.com>2026-02-03 10:03:58 +0800
committerSasha Levin <sashal@kernel.org>2026-03-04 07:20:17 -0500
commit8baa234181f632cabacf73e4834a910859e9fcc9 (patch)
tree71909980efeec7e834cdc2f08b91d43353681e7f /fs
parentfe0ba28c55a5129f286b94f41579bb25318a8e8e (diff)
pstore: ram_core: fix incorrect success return when vmap() fails
[ Upstream commit 05363abc7625cf18c96e67f50673cd07f11da5e9 ] In persistent_ram_vmap(), vmap() may return NULL on failure. If offset is non-zero, adding offset_in_page(start) causes the function to return a non-NULL pointer even though the mapping failed. persistent_ram_buffer_map() therefore incorrectly returns success. Subsequent access to prz->buffer may dereference an invalid address and cause crashes. Add proper NULL checking for vmap() failures. Signed-off-by: Ruipeng Qi <ruipengqi3@gmail.com> Link: https://patch.msgid.link/20260203020358.3315299-1-ruipengqi3@gmail.com Signed-off-by: Kees Cook <kees@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs')
-rw-r--r--fs/pstore/ram_core.c7
1 files changed, 7 insertions, 0 deletions
diff --git a/fs/pstore/ram_core.c b/fs/pstore/ram_core.c
index 03d586f1ebc8..0e58eb7ffac8 100644
--- a/fs/pstore/ram_core.c
+++ b/fs/pstore/ram_core.c
@@ -458,6 +458,13 @@ static void *persistent_ram_vmap(phys_addr_t start, size_t size,
kfree(pages);
/*
+ * vmap() may fail and return NULL. Do not add the offset in this
+ * case, otherwise a NULL mapping would appear successful.
+ */
+ if (!vaddr)
+ return NULL;
+
+ /*
* Since vmap() uses page granularity, we must add the offset
* into the page here, to get the byte granularity address
* into the mapping to represent the actual "start" location.