Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp552190imp; Thu, 21 Feb 2019 06:43:00 -0800 (PST) X-Google-Smtp-Source: AHgI3IbfC8LfU/LtrVWN7DBPndO+MJP6rZVcw2GGorYMeBUDWMjKVxsuCvYRTckj0/+3W1lSOaUR X-Received: by 2002:a17:902:8a91:: with SMTP id p17mr43110488plo.316.1550760180605; Thu, 21 Feb 2019 06:43:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550760180; cv=none; d=google.com; s=arc-20160816; b=N+N8jpT2VUw8W4EjllBvPAjF9rI3z46jt0M7ssV9ZRWVqkrDjuDO3Oh7BqWYuE8sVo IwGYQX88ZSxwTXZiDog0E6WD3qiMIMnOw6RsoXkedK3euEveCj3FzYdZbfLWpX2P3p75 TN3q87G6K3B2ePVhgiRPdvmYG5IDokWyIMq37PFBT97TP5ZtbY+vP9omZUgfFtfSFJ4E w6gmy6Ey3XEqhSb39LHbha7utNjY2SD1CUymze+SN2kzHXnGWO7QFQNG2vgNBIsU0Onz 3L2BSoZ30s2AfnT4llHD7Cg05a8RCVig+pUqLnzbgu8B93/Kp7em46axqxfChzNiW+ce of5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=3qWGKYvJVe6rlXX822jfshk7vgD33C9/lECPdBw1BMA=; b=Ifv61ftoD21sTlbW25CRKRcK4u3eWvYXFgOnc6MboKVoTlB++mzm9tUR112skz3kn8 q7VV32/QpgHKTGpZfrNzC3cvkbh+jAtuC+9nll3Ec8utWm5IjUSvY4ikwCVeSM+hLlif +BufNOJKgBGXASTwp4PbW3SnOTfPlAj7K8lcRF+pEhZsUejKEceSrZThGzpSZ80I2RJi w4uEdwZTwUULJiJ+rd/a0yFxnhu8hu9gjhYGp/eIPchBumamFuqYpJCU6lEnUj9pOrtQ o8fEMfCXfa2duLH+W4hWZvqZkNjLavLfSthzi+UJAsSHW38xxT7MKZ5smgZ8uk+knBFM XkHw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QP+7tqU1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b60si22036776plc.95.2019.02.21.06.42.45; Thu, 21 Feb 2019 06:43:00 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=QP+7tqU1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729122AbfBUOkY (ORCPT + 99 others); Thu, 21 Feb 2019 09:40:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:34858 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729113AbfBUOkX (ORCPT ); Thu, 21 Feb 2019 09:40:23 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A2F7E2084D; Thu, 21 Feb 2019 14:40:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550760023; bh=pqXFUHtbg+D77JgZmUzaXHJtbmDBadv2uNZgJkjzwsI=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=QP+7tqU1muONxQvq8EyRbkYUash+HnrS9friW0+Yhzaqppf8Qw8S5X27hZL/B859t kZuAaGJA5kJGx1OiQpKodhDoB6385depKC6RlZyC5vFJPoczMiAffjyUQv8fkKvjQJ C2lnJm7D6dokqbFBWbNWS0giETlXxvpc3MbyJUC0= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Xiumei Mu , Paolo Abeni , Stefano Garzarella , Jorgen Hansen , "David S. Miller" , Sasha Levin Subject: [PATCH 4.14 04/23] vsock: cope with memory allocation failure at socket creation time Date: Thu, 21 Feb 2019 15:35:46 +0100 Message-Id: <20190221125246.591403675@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190221125246.162644302@linuxfoundation.org> References: <20190221125246.162644302@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit 225d9464268599a5b4d094d02ec17808e44c7553 ] In the unlikely event that the kmalloc call in vmci_transport_socket_init() fails, we end-up calling vmci_transport_destruct() with a NULL vmci_trans() and oopsing. This change addresses the above explicitly checking for zero vmci_trans() at destruction time. Reported-by: Xiumei Mu Fixes: d021c344051a ("VSOCK: Introduce VM Sockets") Signed-off-by: Paolo Abeni Reviewed-by: Stefano Garzarella Reviewed-by: Jorgen Hansen Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- net/vmw_vsock/vmci_transport.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/net/vmw_vsock/vmci_transport.c b/net/vmw_vsock/vmci_transport.c index bf7c516444467..ad3f47a714f36 100644 --- a/net/vmw_vsock/vmci_transport.c +++ b/net/vmw_vsock/vmci_transport.c @@ -1648,6 +1648,10 @@ static void vmci_transport_cleanup(struct work_struct *work) static void vmci_transport_destruct(struct vsock_sock *vsk) { + /* transport can be NULL if we hit a failure at init() time */ + if (!vmci_trans(vsk)) + return; + /* Ensure that the detach callback doesn't use the sk/vsk * we are about to destruct. */ -- 2.19.1