public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org, Vlad Yasevich <vyasevich@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	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
Subject: Re: [PATCH 1/1] sctp: Protect cached endpoints to prevent possible UAF
Date: Thu, 9 Dec 2021 09:16:43 -0300	[thread overview]
Message-ID: <YbHzqwvR+fdrOQim@t14s.localdomain> (raw)
In-Reply-To: <20211208165434.2962062-1-lee.jones@linaro.org>

On Wed, Dec 08, 2021 at 04:54:34PM +0000, Lee Jones wrote:
> The cause of the resultant dump_stack() reported below is a
> dereference of a freed pointer to 'struct sctp_endpoint' in
> sctp_sock_dump().

Hi,

Please give me another day to review this one.

Thanks,
Marcelo

  parent reply	other threads:[~2021-12-09 12:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 16:54 [PATCH 1/1] sctp: Protect cached endpoints to prevent possible UAF Lee Jones
2021-12-08 17:02 ` Lee Jones
2021-12-09 12:21   ` Marcelo Ricardo Leitner
2021-12-09 12:16 ` Marcelo Ricardo Leitner [this message]
2021-12-09 12:42 ` Marcelo Ricardo Leitner
2021-12-09 14:11   ` Lee Jones

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=YbHzqwvR+fdrOQim@t14s.localdomain \
    --to=marcelo.leitner@gmail.com \
    --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=kuba@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=piggy@acm.org \
    --cc=rmlayer@us.ibm.com \
    --cc=sri@us.ibm.com \
    --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