From: Salvatore Mesoraca <s.mesoraca16@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>,
Kees Cook <keescook@chromium.org>,
Solar Designer <solar@openwall.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@xmission.com>,
linux-fsdevel@vger.kernel.org,
Salvatore Mesoraca <s.mesoraca16@gmail.com>
Subject: [kernel-hardening] [RFC v2 0/2] Restrict dangerous open in sticky directories
Date: Tue, 26 Sep 2017 16:14:31 +0200 [thread overview]
Message-ID: <1506435273-8428-1-git-send-email-s.mesoraca16@gmail.com> (raw)
This patch-set introduces two separate features aimed at restricting
dangerous open in world or group writable sticky directories.
The purpose is to prevent exploitable bugs in user-space programs
that don't access sticky directories in the proper way.
The first patch prevents the O_CREAT open of FIFOs and regular files
in world or group writable sticky directories if they already exists
and are owned by someone else.
The second patch prevents O_CREAT open in world or group writable
sticky when the O_EXCL flag is not set, even if the file doesn't
exist yet.
More details can be found in respective commit messages.
Salvatore Mesoraca (2):
Protected FIFOs and regular files
Protected O_CREAT open in sticky directory
Documentation/sysctl/fs.txt | 66 +++++++++++++++++++++++++
fs/namei.c | 118 ++++++++++++++++++++++++++++++++++++++++++--
include/linux/fs.h | 3 ++
kernel/sysctl.c | 27 ++++++++++
4 files changed, 211 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2017-09-26 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 14:14 Salvatore Mesoraca [this message]
2017-09-26 14:14 ` [kernel-hardening] [RFC v2 1/2] Protected FIFOs and regular files Salvatore Mesoraca
2017-09-26 14:14 ` [kernel-hardening] [RFC v2 2/2] Protected O_CREAT open in sticky directory Salvatore Mesoraca
2017-09-26 14:40 ` Jann Horn
2017-09-26 15:13 ` Salvatore Mesoraca
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=1506435273-8428-1-git-send-email-s.mesoraca16@gmail.com \
--to=s.mesoraca16@gmail.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=solar@openwall.com \
--cc=viro@zeniv.linux.org.uk \
/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).