From: Uladzislau Rezki <urezki@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Zorro Lang <zlang@redhat.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
bugzilla-daemon@kernel.org, linux-s390@vger.kernel.org,
linux-xfs@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Uladzislau Rezki <urezki@gmail.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [Bug 216073] New: [s390x] kernel BUG at mm/usercopy.c:101! usercopy: Kernel memory exposure attempt detected from vmalloc 'n o area' (offset 0, size 1)!
Date: Sun, 12 Jun 2022 15:03:20 +0200 [thread overview]
Message-ID: <YqXkGMY9xtUvPR5D@pc638.lan> (raw)
In-Reply-To: <YqXU+oU7wayOcmCe@casper.infradead.org>
> On Sun, Jun 12, 2022 at 12:42:30PM +0800, Zorro Lang wrote:
> > Looks likt it's not a s390x specific bug, I just hit this issue once (not 100%
> > reproducible) on aarch64 with linux v5.19.0-rc1+ [1]. So back to cc linux-mm
> > to get more review.
> >
> > [1]
> > [ 980.200947] usercopy: Kernel memory exposure attempt detected from vmalloc 'no area' (offset 0, size 1)!
>
> if (is_vmalloc_addr(ptr)) {
> struct vm_struct *area = find_vm_area(ptr);
> if (!area) {
> usercopy_abort("vmalloc", "no area", to_user, 0, n);
>
> Oh. Looks like XFS uses vm_map_ram() and vm_map_ram() doesn't allocate
> a vm_struct.
>
> Ulad, how does this look to you?
>
It looks like a correct way to me :) XFS uses per-cpu-vm_map_ram()-vm_unmap_ram()
API which do not allocate "vm_struct" because it is not needed.
>
> diff --git a/mm/usercopy.c b/mm/usercopy.c
> index baeacc735b83..6bc2a1407c59 100644
> --- a/mm/usercopy.c
> +++ b/mm/usercopy.c
> @@ -173,7 +173,7 @@ static inline void check_heap_object(const void *ptr, unsigned long n,
> }
>
> if (is_vmalloc_addr(ptr)) {
> - struct vm_struct *area = find_vm_area(ptr);
> + struct vmap_area *area = find_vmap_area((unsigned long)ptr);
> unsigned long offset;
>
> if (!area) {
> @@ -181,8 +181,9 @@ static inline void check_heap_object(const void *ptr, unsigned long n,
> return;
> }
>
> - offset = ptr - area->addr;
> - if (offset + n > get_vm_area_size(area))
> + /* XXX: We should also abort for free vmap_areas */
> + offset = (unsigned long)ptr - area->va_start;
>
I was a bit confused about "offset" and why it is needed here. It is always zero.
So we can get rid of it to make it less confused. From the other hand a zero offset
contributes to nothing.
>
> + if (offset + n >= area->va_end)
>
I think it is a bit wrong. As i see it, "n" is a size and what we would like to do
here is boundary check:
<snip>
if (n > va_size(area))
usercopy_abort("vmalloc", NULL, to_user, 0, n);
<snip>
--
Uladzislau Rezki
next prev parent reply other threads:[~2022-06-12 13:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-216073-27@https.bugzilla.kernel.org/>
[not found] ` <20220606151312.6a9d098c85ed060d36519600@linux-foundation.org>
[not found] ` <Yp9pHV14OqvH0n02@li-4a3a4a4c-28e5-11b2-a85c-a8d192c6f089.ibm.com>
[not found] ` <20220608021922.n2izu7n4yoadknkx@zlang-mailbox>
[not found] ` <YqD0yAELzHxdRBU6@li-4a3a4a4c-28e5-11b2-a85c-a8d192c6f089.ibm.com>
2022-06-12 4:42 ` Zorro Lang
2022-06-12 11:58 ` Matthew Wilcox
2022-06-12 13:03 ` Uladzislau Rezki [this message]
2022-06-12 17:26 ` Matthew Wilcox
2022-06-12 17:59 ` Yu Zhao
2022-06-12 18:05 ` Matthew Wilcox
2022-06-12 18:43 ` Yu Zhao
2022-06-12 19:52 ` Matthew Wilcox
2022-06-12 20:53 ` Yu Zhao
2022-06-12 19:07 ` Uladzislau Rezki
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=YqXkGMY9xtUvPR5D@pc638.lan \
--to=urezki@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=willy@infradead.org \
--cc=zlang@redhat.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