stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	lksctp developers <linux-sctp@vger.kernel.org>,
	"H.P. Yarroll" <piggy@acm.org>,
	Karl Knutson <karl@athena.chicago.il.us>,
	Jon Grimm <jgrimm@us.ibm.com>,
	Xingang Guo <xingang.guo@intel.com>,
	Hui Huang <hui.huang@nokia.com>,
	Sridhar Samudrala <sri@us.ibm.com>,
	Daisy Chang <daisyc@us.ibm.com>, Ryan Layer <rmlayer@us.ibm.com>,
	Kevin Gao <kevin.gao@intel.com>,
	netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/2] sctp: export sctp_endpoint_{hold,put}() and return incremented endpoint
Date: Fri, 17 Dec 2021 07:06:26 -0800	[thread overview]
Message-ID: <20211217070626.790b8340@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20211217134607.74983-1-lee.jones@linaro.org>

On Fri, 17 Dec 2021 13:46:06 +0000 Lee Jones wrote:
> For example, in sctp_sock_dump(), we could have the following hunk:
> 
> 	sctp_endpoint_hold(tsp->asoc->ep);
> 	ep = tsp->asoc->ep;
> 	sk = ep->base.sk
> 	lock_sock(ep->base.sk);
> 
> It is possible for this task to be swapped out immediately following
> the call into sctp_endpoint_hold() that would change the address of
> tsp->asoc->ep to point to a completely different endpoint.  This means
> a reference could be taken to the old endpoint and the new one would
> be processed without a reference taken, moreover the new endpoint
> could then be freed whilst still processing as a result, causing a
> use-after-free.
> 
> If we return the exact pointer that was held, we ensure this task
> processes only the endpoint we have taken a reference to.  The
> resultant hunk now looks like this:
> 
>       ep = sctp_endpoint_hold(tsp->asoc->ep);
> 	sk = ep->base.sk
> 	lock_sock(sk);

If you have to explain what the next patch will do to make sense 
of this one it really is better to merge the two patches.
Exporting something is not a functional change, nor does it make
the changes easier to review, in fact the opposite is true.

> Fixes: 8f840e47f190c ("sctp: add the sctp_diag.c file")

This patch in itself fixes exactly nothing.

      parent reply	other threads:[~2021-12-17 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 13:46 [PATCH v2 1/2] sctp: export sctp_endpoint_{hold,put}() and return incremented endpoint Lee Jones
2021-12-17 13:46 ` [PATCH v2 2/2] sctp: hold cached endpoints to prevent possible UAF Lee Jones
2021-12-17 14:17 ` [PATCH v2 1/2] sctp: export sctp_endpoint_{hold,put}() and return incremented endpoint David Laight
2021-12-17 14:35   ` Lee Jones
2021-12-19 14:04     ` David Laight
2021-12-17 15:06 ` Jakub Kicinski [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=20211217070626.790b8340@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
    --to=kuba@kernel.org \
    --cc=daisyc@us.ibm.com \
    --cc=davem@davemloft.net \
    --cc=hui.huang@nokia.com \
    --cc=jgrimm@us.ibm.com \
    --cc=karl@athena.chicago.il.us \
    --cc=kevin.gao@intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=piggy@acm.org \
    --cc=rmlayer@us.ibm.com \
    --cc=sri@us.ibm.com \
    --cc=stable@vger.kernel.org \
    --cc=vyasevich@gmail.com \
    --cc=xingang.guo@intel.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;
as well as URLs for NNTP newsgroup(s).