From: Jiri Slaby <jslaby@suse.cz>
To: "Eric W. Biederman" <ebiederm@xmission.com>, stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sasha.levin@oracle.com>,
Jiri Slaby <jirislaby@gmail.com>,
Willy Tarreau <willy@meta-x.org>, Li Zefan <lizefan@huawei.com>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCHES] Bind mount escape fixes (CVE-2015-2925)
Date: Fri, 2 Oct 2015 11:26:01 +0200 [thread overview]
Message-ID: <560E4DA9.4010803@suse.cz> (raw)
In-Reply-To: <87a8s2a7kc.fsf@x220.int.ebiederm.org>
On 10/01/2015, 06:15 PM, Eric W. Biederman wrote:
>
> With a strategically placed rename bind mounts can be tricked into
> giving processes access to the entire filesystem instead of just a piece
> of it. This misfeature has existed since bind mounts were introduced
> into the kernel. This issue has been fixed in Linus's tree and below
> are my tested backports of the fixes to 4.2.1, 4.1.8, 3.18.21, 3.14.53,
> 3.12.48, 3.10.89, 3.4.109, 3.2.71, 2.6.32.68. All of the kernels
> currently listed as being active.
>
> The fixes backported are:
> cde93be45a8a90d8c264c776fab63487b5038a65 dcache: Handle escaped paths in prepend_path
> 397d425dc26da728396e66d392d5dcb8dac30c37 vfs: Test for and handle paths that are unreachable from their mnt_root
>
> As I backported the patches the logical work remained the same but the
> exact implemenation details changed to fit in with the vfs present in
> the older kernels. Minor changes were needed for every the backport to
> every kernel except 4.2.1.
>
> Please queue these changes for the appropriate stable trees.
Applied to 3.12. Thanks!
--
js
suse labs
next prev parent reply other threads:[~2015-10-02 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:15 [PATCHES] Bind mount escape fixes (CVE-2015-2925) Eric W. Biederman
2015-10-01 23:08 ` Willy Tarreau
2015-10-02 2:45 ` Ben Hutchings
2015-10-02 3:28 ` Eric W. Biederman
2015-10-02 16:01 ` Eric W. Biederman
2015-10-03 1:48 ` Ben Hutchings
2015-10-03 6:12 ` Willy Tarreau
2015-10-02 9:26 ` Jiri Slaby [this message]
2015-10-05 10:34 ` Luis Henriques
2015-10-08 1:08 ` Ben Hutchings
2015-10-08 5:11 ` Willy Tarreau
2015-10-18 0:01 ` Greg Kroah-Hartman
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=560E4DA9.4010803@suse.cz \
--to=jslaby@suse.cz \
--cc=ben@decadent.org.uk \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@gmail.com \
--cc=lizefan@huawei.com \
--cc=sasha.levin@oracle.com \
--cc=stable@vger.kernel.org \
--cc=willy@meta-x.org \
/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).