public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "kiyin(尹亮)" <kiyin@tencent.com>
To: Xiaoming Ni <nixiaoming@huawei.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"sameo@linux.intel.com" <sameo@linux.intel.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"mkl@pengutronix.de" <mkl@pengutronix.de>,
	"stefan@datenfreihafen.org" <stefan@datenfreihafen.org>,
	"matthieu.baerts@tessares.net" <matthieu.baerts@tessares.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "wangle6@huawei.com" <wangle6@huawei.com>,
	"xiaoqian9@huawei.com" <xiaoqian9@huawei.com>
Subject: RE: [PATCH 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect()(Internet mail)
Date: Wed, 3 Mar 2021 09:28:11 +0000	[thread overview]
Message-ID: <2965a9b88d254b7f8e7f4356875bbedb@tencent.com> (raw)
In-Reply-To: <20210303061654.127666-5-nixiaoming@huawei.com>

Hi xiaoming,
  the path can only fix the endless loop problem. it can't fix the meaningless llcp_sock->service_name problem.
  if we set llcp_sock->service_name to meaningless string, the connect will be failed. and sk->sk_state will not be LLCP_CONNECTED. then we can call llcp_sock_connect() many times. that leaks everything: llcp_sock->dev, llcp_sock->local, llcp_sock->ssap, llcp_sock->service_name...

Regards,
kiyin.

> -----Original Message-----
> From: Xiaoming Ni [mailto:nixiaoming@huawei.com]
> Sent: Wednesday, March 3, 2021 2:17 PM
> To: linux-kernel@vger.kernel.org; kiyin(尹亮) <kiyin@tencent.com>;
> stable@vger.kernel.org; gregkh@linuxfoundation.org; sameo@linux.intel.com;
> linville@tuxdriver.com; davem@davemloft.net; kuba@kernel.org;
> mkl@pengutronix.de; stefan@datenfreihafen.org;
> matthieu.baerts@tessares.net; netdev@vger.kernel.org
> Cc: nixiaoming@huawei.com; wangle6@huawei.com; xiaoqian9@huawei.com
> Subject: [PATCH 4/4] nfc: Avoid endless loops caused by repeated
> llcp_sock_connect()(Internet mail)
> 
> When sock_wait_state() returns -EINPROGRESS, "sk->sk_state" is
> LLCP_CONNECTING. In this case, llcp_sock_connect() is repeatedly invoked,
>  nfc_llcp_sock_link() will add sk to local->connecting_sockets twice.
>  sk->sk_node->next will point to itself, that will make an endless loop  and
> hang-up the system.
> To fix it, check whether sk->sk_state is LLCP_CONNECTING in
>  llcp_sock_connect() to avoid repeated invoking.
> 
> fix CVE-2020-25673
> Fixes: b4011239a08e ("NFC: llcp: Fix non blocking sockets connections")
> Reported-by: "kiyin(尹亮)" <kiyin@tencent.com>
> Link: https://www.openwall.com/lists/oss-security/2020/11/01/1
> Cc: <stable@vger.kernel.org> #v3.11
> Signed-off-by: Xiaoming Ni <nixiaoming@huawei.com>
> ---
>  net/nfc/llcp_sock.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/net/nfc/llcp_sock.c b/net/nfc/llcp_sock.c index
> 59172614b249..a3b46f888803 100644
> --- a/net/nfc/llcp_sock.c
> +++ b/net/nfc/llcp_sock.c
> @@ -673,6 +673,10 @@ static int llcp_sock_connect(struct socket *sock,
> struct sockaddr *_addr,
>  		ret = -EISCONN;
>  		goto error;
>  	}
> +	if (sk->sk_state == LLCP_CONNECTING) {
> +		ret = -EINPROGRESS;
> +		goto error;
> +	}
> 
>  	dev = nfc_get_device(addr->dev_idx);
>  	if (dev == NULL) {
> --
> 2.27.0
> 


  reply	other threads:[~2021-03-03 13:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03  6:16 [PATCH 0/4] nfc: fix Resource leakage and endless loop Xiaoming Ni
2021-03-03  6:16 ` [PATCH 1/4] nfc: fix refcount leak in llcp_sock_bind() Xiaoming Ni
2021-03-03  6:16 ` [PATCH 2/4] nfc: fix refcount leak in llcp_sock_connect() Xiaoming Ni
2021-03-03  6:16 ` [PATCH 3/4] nfc: fix memory " Xiaoming Ni
2021-03-03  6:16 ` [PATCH 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect() Xiaoming Ni
2021-03-03  9:28   ` kiyin(尹亮) [this message]
2021-03-05  3:24     ` [PATCH 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect()(Internet mail) Xiaoming Ni
2021-03-23 13:43 ` [PATCH 0/4] nfc: fix Resource leakage and endless loop Greg KH
2021-03-25  3:51   ` [PATCH resend " Xiaoming Ni
2021-03-25  3:51     ` [PATCH resend 1/4] nfc: fix refcount leak in llcp_sock_bind() Xiaoming Ni
2021-03-25  3:51     ` [PATCH resend 2/4] nfc: fix refcount leak in llcp_sock_connect() Xiaoming Ni
2021-03-25  3:51     ` [PATCH resend 3/4] nfc: fix memory " Xiaoming Ni
2021-03-25  3:51     ` [PATCH resend 4/4] nfc: Avoid endless loops caused by repeated llcp_sock_connect() Xiaoming Ni
2021-03-26  0:30     ` [PATCH resend 0/4] nfc: fix Resource leakage and endless loop patchwork-bot+netdevbpf

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=2965a9b88d254b7f8e7f4356875bbedb@tencent.com \
    --to=kiyin@tencent.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=nixiaoming@huawei.com \
    --cc=sameo@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=stefan@datenfreihafen.org \
    --cc=wangle6@huawei.com \
    --cc=xiaoqian9@huawei.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