From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ilya Matveychikov <matvejchikov@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] ksys_mount: check for permissions before resource allocation
Date: Tue, 5 Jun 2018 12:26:41 +0100 [thread overview]
Message-ID: <20180605112641.GN30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <BD48252B-65D7-4238-BDA2-71BAC1CEA855@gmail.com>
On Tue, Jun 05, 2018 at 10:59:51AM +0400, Ilya Matveychikov wrote:
> Just CC’ed to some of maintainers.
>
> $ perl scripts/get_maintainer.pl fs/0001-ksys_mount-check-for-permissions-before-resource-all.patch
> Alexander Viro <viro@zeniv.linux.org.uk> (maintainer:FILESYSTEMS (VFS and infrastructure))
> linux-fsdevel@vger.kernel.org (open list:FILESYSTEMS (VFS and infrastructure))
> linux-kernel@vger.kernel.org (open list)
>
> > On Jun 5, 2018, at 6:00 AM, Ilya Matveychikov <matvejchikov@gmail.com> wrote:
> >
> > Early check for mount permissions prevents possible allocation of 3
> > pages from kmalloc() pool by unpriveledged user which can be used for
> > spraying the kernel heap.
I'm sorry, but there are arseloads of unpriveleged syscalls that do the same,
starting with read() from procfs files. So what the hell does it buy?
next prev parent reply other threads:[~2018-06-05 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D2317950-0DB0-4311-ADB1-FF677B676E04@gmail.com>
2018-06-05 6:59 ` [PATCH] ksys_mount: check for permissions before resource allocation Ilya Matveychikov
2018-06-05 11:26 ` Al Viro [this message]
2018-06-05 11:35 ` Ilya Matveychikov
2018-06-05 11:53 ` Al Viro
2018-06-05 12:07 ` Ilya Matveychikov
2018-06-05 12:28 ` David Sterba
2018-06-05 12:42 ` Ilya Matveychikov
2018-06-05 12:34 ` Al Viro
2018-06-05 19:56 ` Eric W. Biederman
2018-06-06 9:32 ` Ilya Matveychikov
2018-06-06 14:22 ` Eric W. Biederman
2018-06-06 15:26 ` Ilya Matveychikov
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=20180605112641.GN30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matvejchikov@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;
as well as URLs for NNTP newsgroup(s).