From: Holger Eitzenberger <holger@eitzenberger.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel <netfilter-devel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>
Subject: Re: [OOPS,xt_owner,V2]: Oops accessing socket in owner_mt()
Date: Mon, 11 Aug 2014 14:40:36 +0200 [thread overview]
Message-ID: <20140811124035.GP3549@imap.eitzenberger.org> (raw)
In-Reply-To: <20140428155731.GA29816@localhost>
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
Hi Pablo,
> Not your fault, but I think we should also check for ...
>
> ... || skb->sk->sk_state == TCP_TIME_WAIT)
>
> since early demux was introduced, we may have skb->sk pointing to a
> timewait socket.
the following patch is still in my patch queue. I have updated
it to handle TIME_WAIT sockets, like you requested.
In the meantime I have had some more systems requiring this
patch, issue didn't occur afterwards. Please apply.
Thanks!
/Holger
[-- Attachment #2: xt_owner-fix.diff --]
[-- Type: text/x-diff, Size: 2488 bytes --]
xt_owner: fix race with sock_orphan()
By using a read_lock on sk->sk_callback_lock we can avoid Oops
due to someone else calling sock_orphan() at same time on
another CPU, e. g. when using TPROXY.
Signed-off-by: Holger Eitzenberger <holger@eitzenberger.org>
Index: linux-3.8.y/net/netfilter/xt_owner.c
===================================================================
--- linux-3.8.y.orig/net/netfilter/xt_owner.c
+++ linux-3.8.y/net/netfilter/xt_owner.c
@@ -14,6 +14,7 @@
#include <linux/skbuff.h>
#include <linux/file.h>
#include <net/sock.h>
+#include <net/tcp.h>
#include <linux/netfilter/x_tables.h>
#include <linux/netfilter/xt_owner.h>
@@ -32,21 +33,32 @@ static bool
owner_mt(const struct sk_buff *skb, struct xt_action_param *par)
{
const struct xt_owner_match_info *info = par->matchinfo;
+ struct sock *sk = skb->sk;
const struct file *filp;
- if (skb->sk == NULL || skb->sk->sk_socket == NULL)
+ if (sk == NULL || sk->sk_state == TCP_TIME_WAIT)
return (info->match ^ info->invert) == 0;
- else if (info->match & info->invert & XT_OWNER_SOCKET)
+
+ read_lock_bh(&sk->sk_callback_lock);
+
+ if (sk->sk_socket == NULL) {
+ read_unlock_bh(&sk->sk_callback_lock);
+ return (info->match ^ info->invert) == 0;
+ }
+
+ if (info->match & info->invert & XT_OWNER_SOCKET)
/*
* Socket exists but user wanted ! --socket-exists.
* (Single ampersands intended.)
*/
- return false;
+ goto out_false;
- filp = skb->sk->sk_socket->file;
- if (filp == NULL)
+ filp = sk->sk_socket->file;
+ if (filp == NULL) {
+ read_unlock_bh(&sk->sk_callback_lock);
return ((info->match ^ info->invert) &
(XT_OWNER_UID | XT_OWNER_GID)) == 0;
+ }
if (info->match & XT_OWNER_UID) {
kuid_t uid_min = make_kuid(&init_user_ns, info->uid_min);
@@ -54,7 +66,7 @@ owner_mt(const struct sk_buff *skb, stru
if ((uid_gte(filp->f_cred->fsuid, uid_min) &&
uid_lte(filp->f_cred->fsuid, uid_max)) ^
!(info->invert & XT_OWNER_UID))
- return false;
+ goto out_false;
}
if (info->match & XT_OWNER_GID) {
@@ -63,10 +75,16 @@ owner_mt(const struct sk_buff *skb, stru
if ((gid_gte(filp->f_cred->fsgid, gid_min) &&
gid_lte(filp->f_cred->fsgid, gid_max)) ^
!(info->invert & XT_OWNER_GID))
- return false;
+ goto out_false;
}
+ read_unlock_bh(&sk->sk_callback_lock);
+
return true;
+
+out_false:
+ read_unlock_bh(&sk->sk_callback_lock);
+ return false;
}
static struct xt_match owner_mt_reg __read_mostly = {
prev parent reply other threads:[~2014-08-11 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 13:32 [OOPS,TPROXY,xt_owner]: Oops accessing socket in owner_mt() Holger Eitzenberger
2014-04-28 15:57 ` Pablo Neira Ayuso
2014-04-28 16:20 ` Eric Dumazet
2014-04-28 16:43 ` Holger Eitzenberger
2014-08-11 12:40 ` Holger Eitzenberger [this message]
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=20140811124035.GP3549@imap.eitzenberger.org \
--to=holger@eitzenberger.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).