From: Dave Jones <davej@codemonkey.org.uk>
To: Tyler Hicks <tyhicks@canonical.com>
Cc: Kees Cook <keescook@chromium.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: out of bounds strscpy from seccomp_actions_logged_handler
Date: Tue, 24 Oct 2017 20:18:31 -0400 [thread overview]
Message-ID: <20171025001831.avuyouhphfdc42bq@codemonkey.org.uk> (raw)
In-Reply-To: <8d59f73f-3ecb-277d-1e70-682792689a6d@canonical.com>
On Tue, Oct 24, 2017 at 06:54:25PM -0500, Tyler Hicks wrote:
> On 10/24/2017 06:46 PM, Dave Jones wrote:
> > (Triggered with trinity, but it seems just a 'cat
> > /proc/sys/kernel/seccomp/actions_logged' reproduces just as easily).
>
> Hi Dave - Thanks for the report. This is a false positive that was
> previously discussed here:
>
> https://lkml.kernel.org/r/<20171010182805.52b9b2af@cakuba.netronome.com>
Bah, I thought this smelled familiar. I'll just roll Andrey's
workaround diff into my builds for fuzzing runs until someone figures
out something better.
Dave
prev parent reply other threads:[~2017-10-25 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 23:46 Dave Jones
2017-10-24 23:54 ` Tyler Hicks
2017-10-25 0:18 ` Dave Jones [this message]
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=20171025001831.avuyouhphfdc42bq@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@canonical.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
all inboxes | Powered by JetHome®