From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
Kees Cook <keescook@chromium.org>,
syzbot+3ad9614a12f80994c32e@syzkaller.appspotmail.com,
Tycho Andersen <tycho@tycho.pizza>
Subject: [GIT PULL] seccomp fixes for v5.9-rc5
Date: Fri, 11 Sep 2020 17:20:02 -0700 [thread overview]
Message-ID: <202009111718.B94EAD7@keescook> (raw)
Hi Linus,
Please pull these seccomp fixes for v5.9-rc5. This fixes a rare race
condition in seccomp when using TSYNC and USER_NOTIF together where a
memory allocation would not get freed (found by syzkaller, fixed by
Tycho). Additionally updates Tycho's MAINTAINERS and .mailmap entries
for his new address.
Thanks!
-Kees
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-v5.9-rc5
for you to fetch changes up to e839317900e9f13c83d8711d684de88c625b307a:
seccomp: don't leave dangling ->notif if file allocation fails (2020-09-08 11:30:16 -0700)
----------------------------------------------------------------
seccomp fixes for v5.9-rc5
- Fix memory resource leak of user_notif under TSYNC race (Tycho Andersen)
----------------------------------------------------------------
Tycho Andersen (3):
seccomp: don't leak memory when filter install races
mailmap, MAINTAINERS: move to tycho.pizza
seccomp: don't leave dangling ->notif if file allocation fails
.mailmap | 1 +
MAINTAINERS | 2 +-
kernel/seccomp.c | 24 ++++++++++++++++++------
3 files changed, 20 insertions(+), 7 deletions(-)
--
Kees Cook
next reply other threads:[~2020-09-12 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 0:20 Kees Cook [this message]
2020-09-12 20:00 ` [GIT PULL] seccomp fixes for v5.9-rc5 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=202009111718.B94EAD7@keescook \
--to=keescook@chromium.org \
--cc=christian.brauner@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+3ad9614a12f80994c32e@syzkaller.appspotmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tycho@tycho.pizza \
/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).