From: Jan Kara <jack@suse.cz>
To: Amir Goldstein <amir73il@gmail.com>
Cc: keescook@chromium.org, Jan Kara <jack@suse.cz>,
xypron.glpk@gmx.de, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fanotify: Make sure to check event_len when copying
Date: Wed, 5 Dec 2018 13:10:36 +0100 [thread overview]
Message-ID: <20181205121036.GB30615@quack2.suse.cz> (raw)
In-Reply-To: <CAOQ4uxg3jaQWpRNxSRuT2VRvAcQTNkBLVr3GPtX3ekQPE7k-Dg@mail.gmail.com>
On Wed 05-12-18 09:15:44, Amir Goldstein wrote:
> On Wed, Dec 5, 2018 at 1:44 AM Kees Cook <keescook@chromium.org> wrote:
> >
> > As a precaution, make sure we check event_len when copying to userspace.
> > Based on old feedback: https://lkml.kernel.org/r/542D9FE5.3010009@gmx.de
> >
>
> This precaution serves the new fanotify_event_info_fid format well:
> https://marc.info/?l=linux-fsdevel&m=154375073318106&w=2
> but also conflicts with my series.
>
> I can weave your patch into my series and add a similar sanity check in
> copy_fid_to_user() or if Jan applies your patch and has more comments
> on my v4 series, I'll rebase on top of that.
Yeah, I don't think there's any need for you to rebase just now. Either
I'll fixup your patch or you'll do the rebase if there are further changes
to the series...
Honza
>
> Thanks,
> Amir.
>
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> > ---
> > fs/notify/fanotify/fanotify_user.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/fs/notify/fanotify/fanotify_user.c b/fs/notify/fanotify/fanotify_user.c
> > index e03be5071362..d9484a0ac6b3 100644
> > --- a/fs/notify/fanotify/fanotify_user.c
> > +++ b/fs/notify/fanotify/fanotify_user.c
> > @@ -206,7 +206,7 @@ static int process_access_response(struct fsnotify_group *group,
> >
> > static ssize_t copy_event_to_user(struct fsnotify_group *group,
> > struct fsnotify_event *event,
> > - char __user *buf)
> > + char __user *buf, size_t count)
> > {
> > struct fanotify_event_metadata fanotify_event_metadata;
> > struct file *f;
> > @@ -220,6 +220,12 @@ static ssize_t copy_event_to_user(struct fsnotify_group *group,
> >
> > fd = fanotify_event_metadata.fd;
> > ret = -EFAULT;
> > + /*
> > + * Sanity check copy size in case get_one_event() and
> > + * fill_event_metadata() event_len sizes ever get out of sync.
> > + */
> > + if (WARN_ON_ONCE(fanotify_event_metadata.event_len > count))
> > + goto out_close_fd;
> > if (copy_to_user(buf, &fanotify_event_metadata,
> > fanotify_event_metadata.event_len))
> > goto out_close_fd;
> > @@ -295,7 +301,7 @@ static ssize_t fanotify_read(struct file *file, char __user *buf,
> > continue;
> > }
> >
> > - ret = copy_event_to_user(group, kevent, buf);
> > + ret = copy_event_to_user(group, kevent, buf, count);
> > if (unlikely(ret == -EOPENSTALE)) {
> > /*
> > * We cannot report events with stale fd so drop it.
> > --
> > 2.17.1
> >
> >
> > --
> > Kees Cook
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2018-12-05 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 23:44 [PATCH] fanotify: Make sure to check event_len when copying Kees Cook
2018-12-05 7:15 ` Amir Goldstein
2018-12-05 12:10 ` Jan Kara [this message]
2018-12-05 12:09 ` Jan Kara
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=20181205121036.GB30615@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xypron.glpk@gmx.de \
/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