From: Patrick McHardy <kaber@trash.net>
To: Simon Horman <horms@verge.net.au>
Cc: netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
Wensong Zhang <wensong@linux-vs.org>,
Julian Anastasov <ja@ssi.bg>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] ipvs: Add boundary check on ioctl arguments
Date: Mon, 04 Jan 2010 14:59:47 +0100 [thread overview]
Message-ID: <4B41F453.1090802@trash.net> (raw)
In-Reply-To: <20091229015822.GF10172@verge.net.au>
Simon Horman wrote:
> From: Arjan van de Ven <arjan@linux.intel.com>
>
> ipvs: Add boundary check on ioctl arguments
>
> The ipvs code has a nifty system for doing the size of ioctl command
> copies; it defines an array with values into which it indexes the cmd
> to find the right length.
>
> Unfortunately, the ipvs code forgot to check if the cmd was in the
> range that the array provides, allowing for an index outside of the
> array, which then gives a "garbage" result into the length, which
> then gets used for copying into a stack buffer.
>
> Fix this by adding sanity checks on these as well as the copy size.
>
> [ horms@verge.net.au: adjusted limit to IP_VS_SO_GET_MAX ]
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> Acked-by: Julian Anastasov <ja@ssi.bg>
> Signed-off-by: Simon Horman <horms@verge.net.au>
>
> ---
>
> net/netfilter/ipvs/ip_vs_ctl.c | 14 +++++++++++++-
> 1 files changed, 13 insertions(+), 1 deletions(-)
>
> Hi Arjen,
>
> this is the 4th response to your patch. I am guessing the previous
> ones didn't reach you for some reason. And I guess this one wont
> for the same reason.
>
> I agree with Julian's assessment that your patch shouldn't be
> necessary, but on the other hand I think that the checks are
> reasonable. Your original patch made checks of the form of
> "cmd > IP_VS_SO_GET_MAX + 1". I have updated this to
> "cmd > IP_VS_SO_GET_MAX", as suggested by Julian, as the optmax
> elements of struct nf_sockopt_ops set a non-inclusive range.
>
> http://lkml.indiana.edu/hypermail/linux/kernel/0910.0/00852.html
>
> Index: net-next-2.6/net/netfilter/ipvs/ip_vs_ctl.c
As a bugfix, this seems more appropriate for net-2.6.git. Please let
me know which tree you want me to apply this to.
next prev parent reply other threads:[~2010-01-04 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 1:58 [PATCH] ipvs: Add boundary check on ioctl arguments Simon Horman
2010-01-04 13:59 ` Patrick McHardy [this message]
2010-01-04 15:34 ` Arjan van de Ven
2010-01-04 15:39 ` Patrick McHardy
2010-01-04 23:25 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2009-09-30 11:11 Arjan van de Ven
2009-09-30 13:38 ` Hannes Eder
2009-09-30 15:18 ` Arjan van de Ven
2009-09-30 15:33 ` Hannes Eder
2009-09-30 19:41 ` Julian Anastasov
2009-10-01 7:22 ` Arjan van de Ven
2009-10-02 8:35 ` Julian Anastasov
2009-12-15 6:17 ` Arjan van de Ven
2009-12-15 6:32 ` Simon Horman
2009-12-24 4:16 ` Simon Horman
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=4B41F453.1090802@trash.net \
--to=kaber@trash.net \
--cc=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wensong@linux-vs.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).