From: Dev Jain <dev.jain@arm.com>
To: kees@kernel.org, akpm@linux-foundation.org
Cc: Dev Jain <dev.jain@arm.com>,
gustavoars@kernel.org, linux-hardening@vger.kernel.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ryan.roberts@arm.com, anshuman.khandual@arm.com,
david@kernel.org, urezki@gmail.com
Subject: [PATCH] mm/usercopy: harden bounds checking for vmalloc allocations
Date: Wed, 22 Jul 2026 14:29:35 +0000 [thread overview]
Message-ID: <20260722142936.3287702-1-dev.jain@arm.com> (raw)
The vmalloc allocator stores the actual allocation size inside the
vm_struct structure. We can use this bound in usercopy instead of the
page-aligned va_end to catch usercopy beyond the actual allocation size.
For vmap, the requested_size field is always page-aligned since it maps a
certain number of pages. Same for vm_map_ram (alongwith, not even having
a vm_struct). So the check is only relevant for vmalloc mappings.
Because there are early vm areas registered even before vmalloc_init,
requested_size may be zero. So also check whether the requested_size
is set.
Signed-off-by: Dev Jain <dev.jain@arm.com>
---
Applies on mm-new (3d18f3499c48).
mm/usercopy.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/mm/usercopy.c b/mm/usercopy.c
index 5de7a518b1b1c..772681aff8477 100644
--- a/mm/usercopy.c
+++ b/mm/usercopy.c
@@ -176,10 +176,28 @@ static inline void check_heap_object(const void *ptr, unsigned long n,
if (is_vmalloc_addr(ptr) && !pagefault_disabled()) {
struct vmap_area *area = find_vmap_area(addr);
+ struct vm_struct *vm;
if (!area)
usercopy_abort("vmalloc", "no area", to_user, 0, n);
+ vm = area->vm;
+ /*
+ * Mappings with a vm_struct track the originally requested
+ * size. Check against that rather than the page-rounded
+ * vmap_area->va_end so copies cannot reach vmalloc tail
+ * padding. vmap mappings are always page aligned.
+ */
+ if (vm && (vm->flags & VM_ALLOC) && vm->requested_size) {
+ unsigned long size = vm->requested_size;
+
+ offset = addr - area->va_start;
+ if (offset > size || n > size - offset)
+ usercopy_abort("vmalloc", NULL, to_user,
+ offset, n);
+ return;
+ }
+
if (n > area->va_end - addr) {
offset = addr - area->va_start;
usercopy_abort("vmalloc", NULL, to_user, offset, n);
--
2.43.0
reply other threads:[~2026-07-22 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260722142936.3287702-1-dev.jain@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@kernel.org \
--cc=gustavoars@kernel.org \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=urezki@gmail.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