From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
James Morris <jamorris@linux.microsoft.com>,
syzbot+b562969adb2e04af3442@syzkaller.appspotmail.com,
Tycho Andersen <tycho@tycho.ws>
Subject: [GIT PULL] seccomp fixes for v5.1-rc8
Date: Mon, 29 Apr 2019 12:58:36 -0700 [thread overview]
Message-ID: <20190429195836.GA30688@beast> (raw)
Hi Linus,
Please pull these seccomp fixes for v5.1-rc8. Syzbot found a use-after-free
bug in seccomp due to flags that should not be allowed to be used together.
Tycho fixed this, I updated the self-tests, and the syzkaller PoC has been
running for several days without triggering KASan (before this fix, it
would reproduce). These patches have also been in -next for almost a week,
just to be sure.
Thanks!
-Kees
The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:
Linux 5.1-rc2 (2019-03-24 14:02:26 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.1-rc8
for you to fetch changes up to 7a0df7fbc14505e2e2be19ed08654a09e1ed5bf6:
seccomp: Make NEW_LISTENER and TSYNC flags exclusive (2019-04-25 15:55:58 -0700)
----------------------------------------------------------------
seccomp use-after-free fix
- Add logic for making some seccomp flags exclusive (Tycho)
- Update selftests for exclusivity testing (Kees)
----------------------------------------------------------------
Kees Cook (1):
selftests/seccomp: Prepare for exclusive seccomp flags
Tycho Andersen (1):
seccomp: Make NEW_LISTENER and TSYNC flags exclusive
kernel/seccomp.c | 17 ++++++++++++--
tools/testing/selftests/seccomp/seccomp_bpf.c | 34 ++++++++++++++++++++-------
2 files changed, 40 insertions(+), 11 deletions(-)
--
Kees Cook
next reply other threads:[~2019-04-29 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 19:58 Kees Cook [this message]
2019-04-29 22:10 ` [GIT PULL] seccomp fixes for v5.1-rc8 pr-tracker-bot
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=20190429195836.GA30688@beast \
--to=keescook@chromium.org \
--cc=jamorris@linux.microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+b562969adb2e04af3442@syzkaller.appspotmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tycho@tycho.ws \
/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).