From: Jay Fenlason <fenlason@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: johunt@akamai.com, netdev@vger.kernel.org,
venkat.x.venkatsubra@oracle.com, linux-kernel@vger.kernel.org,
jjolly@suse.com, honli@redhat.com
Subject: Re: [PATCH] rds: fix local ping DoS
Date: Thu, 14 Nov 2013 15:47:59 -0500 [thread overview]
Message-ID: <20131114204758.GA22417@redhat.com> (raw)
In-Reply-To: <20131114.020355.1973894145326845195.davem@davemloft.net>
On Thu, Nov 14, 2013 at 02:03:55AM -0500, David Miller wrote:
> From: Josh Hunt <johunt@akamai.com>
> Date: Wed, 13 Nov 2013 17:15:43 -0800
>
> > The rds_ib_xmit function in net/rds/ib_send.c in the Reliable Datagram Sockets
> > (RDS) protocol implementation allows local users to cause a denial of service
> > (BUG_ON and kernel panic) by establishing an RDS connection with the source
> > IP address equal to the IPoIB interface's own IP address, as demonstrated by
> > rds-ping.
> >
> > A local unprivileged user could use this flaw to crash the system.
> >
> > CVE-2012-2372
> >
> > Reported-by: Honggang Li <honli@redhat.com>
> > Signed-off-by: Josh Hunt <johunt@akamai.com>
>
> I'm sorry I can't apply this. This commit message needs to be much
> less terse and explain things more.
>
> First of all, why is the "off % RDS_FRAG_SIZE" important?
>
> And, even more importantly, why is is OK to avoid this assertion just
> because we're going over loopback?
>
> Furthermore, why doesn't net/rds/iw_send.c:rds_iw_xmit() have the same
> exact problem? It makes the same exact assertion check.
>
> I know this RDS code is a steaming pile of poo, but that doesn't mean
> we just randomly adjust assertions to make crashes go away without
> sufficient understanding of exactly what's going on.
And that is why rds should be moved to staging, where nobody will
accidentally think that it is actually being maintained.
-- JF
prev parent reply other threads:[~2013-11-14 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 1:15 [PATCH] rds: fix local ping DoS Josh Hunt
2013-11-14 7:03 ` David Miller
2013-11-14 13:45 ` Josh Hunt
2013-11-14 20:47 ` Jay Fenlason [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=20131114204758.GA22417@redhat.com \
--to=fenlason@redhat.com \
--cc=davem@davemloft.net \
--cc=honli@redhat.com \
--cc=jjolly@suse.com \
--cc=johunt@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=venkat.x.venkatsubra@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.