From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: netfilter-devel@vger.kernel.org
Cc: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Subject: [PATCH 0/3] Nfnetlink and ipset fixes
Date: Thu, 28 Jun 2012 15:57:46 +0300 [thread overview]
Message-ID: <1340888269-4926-1-git-send-email-tomasz.bursztyka@linux.intel.com> (raw)
Hi,
The 2 first patches fixes the same issue, but in 2 different place.
Patch 1:
So here is how the issue can be reprocuced:
Create a netlink message, targeting ipset subsystem. And send a command on id 0 (IPSET_CMD_NONE):
This will lead to a crash on line 188 of nfnetlink.c since nc->call is NULL (so you get a NULL dereference).
Or Patch 2:
Same issue.
It fixes ipset to handle the IPSET_CMD_NONE, return -EOPNOTSUPP.
Patch 3:
While doing patch 1 I figured out rcu_read_unlock() is not called in case nla_parse() error, so it fixes it.
Br,
Tomasz Bursztyka (3):
nfnetlink: Check callbacks before using those in nfnetlink_rcv_msg
ipset: Handle properly an IPSET_CMD_NONE
nfnetlink: Unlock a previously locked rcu_read in nfnetlink_rcv_msg
net/netfilter/ipset/ip_set_core.c | 12 ++++++++++++
net/netfilter/nfnetlink.c | 8 ++++++--
2 files changed, 18 insertions(+), 2 deletions(-)
--
1.7.8.6
next reply other threads:[~2012-06-28 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 12:57 Tomasz Bursztyka [this message]
2012-06-28 12:57 ` [PATCH 1/3] nfnetlink: Check callbacks before using those in nfnetlink_rcv_msg Tomasz Bursztyka
2012-06-29 11:15 ` Pablo Neira Ayuso
2012-06-29 19:03 ` Jan Engelhardt
2012-06-30 8:54 ` Florian Westphal
2012-07-04 20:54 ` Pablo Neira Ayuso
2012-06-28 12:57 ` [PATCH 2/3] ipset: Handle properly an IPSET_CMD_NONE Tomasz Bursztyka
2012-06-28 14:40 ` Jozsef Kadlecsik
2012-06-29 11:13 ` Pablo Neira Ayuso
2012-06-28 12:57 ` [PATCH 3/3] nfnetlink: Unlock a previously locked rcu_read in nfnetlink_rcv_msg Tomasz Bursztyka
2012-06-28 13:30 ` Eric Dumazet
2012-06-29 11:13 ` Pablo Neira Ayuso
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=1340888269-4926-1-git-send-email-tomasz.bursztyka@linux.intel.com \
--to=tomasz.bursztyka@linux.intel.com \
--cc=netfilter-devel@vger.kernel.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).