From: ebiederm@xmission.com (Eric W. Biederman)
To: David Miller <davem@davemloft.net>
Cc: Kees Cook <keescook@chromium.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Richard Weinberger <richard@nod.at>,
bridge@lists.linux-foundation.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net] bridge: Only call /sbin/bridge-stp for the initial network namespace
Date: Mon, 30 Nov 2015 15:38:15 -0600 [thread overview]
Message-ID: <87egf7183c.fsf_-_@x220.int.ebiederm.org> (raw)
In-Reply-To: <CAGXu5jJqQKAmFK0nL69E0QOpo8WSVDqStGZo7-m7gy3vnXBa=A@mail.gmail.com> (Kees Cook's message of "Mon, 30 Nov 2015 12:14:41 -0800")
There is no defined mechanism to pass network namespace information
into /sbin/bridge-stp therefore don't even try to invoke it except
for bridge devices in the initial network namespace.
It is possible for unprivileged users to cause /sbin/bridge-stp to be
invoked for any network device name which if /sbin/bridge-stp does not
guard against unreasonable arguments or being invoked twice on the same
network device could cause problems.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
---
net/bridge/br_stp_if.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/net/bridge/br_stp_if.c b/net/bridge/br_stp_if.c
index 5396ff08af32..742fa89528ab 100644
--- a/net/bridge/br_stp_if.c
+++ b/net/bridge/br_stp_if.c
@@ -142,7 +142,9 @@ static void br_stp_start(struct net_bridge *br)
char *envp[] = { NULL };
struct net_bridge_port *p;
- r = call_usermodehelper(BR_STP_PROG, argv, envp, UMH_WAIT_PROC);
+ r = -ENOENT;
+ if (dev_net(br->dev) == &init_net)
+ r = call_usermodehelper(BR_STP_PROG, argv, envp, UMH_WAIT_PROC);
spin_lock_bh(&br->lock);
--
2.2.1
next prev parent reply other threads:[~2015-11-30 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 22:43 user controllable usermodehelper in br_stp_if.c Richard Weinberger
2015-11-30 20:14 ` Kees Cook
2015-11-30 21:38 ` Eric W. Biederman [this message]
2015-11-30 22:12 ` [PATCH net] bridge: Only call /sbin/bridge-stp for the initial network namespace Stephen Hemminger
2015-11-30 22:16 ` Eric W. Biederman
2015-11-30 22:57 ` Richard Weinberger
2015-12-01 14:13 ` Hannes Frederic Sowa
2015-12-03 4:50 ` David Miller
2015-12-08 20:56 ` Kees Cook
2015-11-30 23:03 ` user controllable usermodehelper in br_stp_if.c Richard Weinberger
-- strict thread matches above, loose matches on Subject: below --
2016-01-05 9:46 [PATCH net] bridge: Only call /sbin/bridge-stp for the initial network namespace Hannes Frederic Sowa
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=87egf7183c.fsf_-_@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richard@nod.at \
/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).