From: Ben Hutchings <ben@decadent.org.uk>
To: Quentin Casasnovas <quentin.casasnovas@oracle.com>,
santosh shilimkar <santosh.shilimkar@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Vegard Nossum <vegard.nossum@oracle.com>,
Sasha Levin <sasha.levin@oracle.com>,
Chien Yen <chien.yen@oracle.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] RDS: fix race condition when sending a message on unbound socket.
Date: Tue, 24 Nov 2015 18:25:47 +0000 [thread overview]
Message-ID: <1448389547.27159.8.camel@decadent.org.uk> (raw)
In-Reply-To: <20151103112545.GD921@chrystal.uk.oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1561 bytes --]
On Tue, 2015-11-03 at 12:25 +0100, Quentin Casasnovas wrote:
> On Fri, Oct 16, 2015 at 10:47:49AM -0700, santosh shilimkar wrote:
> > On 10/16/2015 8:11 AM, Quentin Casasnovas wrote:
> > > Sasha's found a NULL pointer dereference in the RDS connection code when
> > > sending a message to an apparently unbound socket. The problem is caused
> > > by the code checking if the socket is bound in rds_sendmsg(), which checks
> > > the rs_bound_addr field without taking a lock on the socket. This opens a
> > > race where rs_bound_addr is temporarily set but where the transport is not
> > > in rds_bind(), leading to a NULL pointer dereference when trying to
> > > dereference 'trans' in __rds_conn_create().
> > >
> > > Vegard wrote a reproducer for this issue, so kindly ask him to share if
> > > you're interested.
> > >
> > > I cannot reproduce the NULL pointer dereference using Vegard's reproducer
> > > with this patch, whereas I could without.
> > >
> > > Complete earlier incomplete fix to CVE-2015-6937:
> > >
> > > 74e98eb08588 ("RDS: verify the underlying transport exists before creating a connection")
> > >
>
> For reference, this has been assigned CVE-2015-7990 on the oss-sec thread:
>
> http://seclists.org/oss-sec/2015/q4/179
But the patch doesn't seem to have gone anywhere. Santosh, can you
apply this in your tree and ask David to pull, or should Quentin re-
send it to netdev?
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-11-24 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 15:11 Quentin Casasnovas
2015-10-16 17:47 ` santosh shilimkar
2015-11-03 11:25 ` Quentin Casasnovas
2015-11-03 16:27 ` santosh shilimkar
2015-11-24 18:25 ` Ben Hutchings [this message]
2015-11-24 18:43 ` santosh shilimkar
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=1448389547.27159.8.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=chien.yen@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin.casasnovas@oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=sasha.levin@oracle.com \
--cc=vegard.nossum@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®