Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp548769imp; Thu, 21 Feb 2019 06:39:15 -0800 (PST) X-Google-Smtp-Source: AHgI3IbsqBysTLtvORIY6cbXY184cXoXFt9iorZbrRputkiQbDCSetZCXUaeSkiBEMvUDJwGw+I3 X-Received: by 2002:a62:5c87:: with SMTP id q129mr28355129pfb.180.1550759955609; Thu, 21 Feb 2019 06:39:15 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550759955; cv=none; d=google.com; s=arc-20160816; b=MP+UX/mNlQSkGKzO5iA8SwfWDFQP9A8ZtXIUfK0zBlNSHSqzTHJxhHYKMuyl+s0Dbz IRSABySwhoVdH8Wla4EKU5G58PkW2UTxxRfrCa0e7MYWj55dsk21q9sA9G3njGpupcsz S1l6/63z3YmuJHydjRVkSNMmjKbKPjj4lOHRA72HwGfn6kTYXK4EY55j2ZwUHIJWUPdf 8kAb+qQEiBThmyilVkAySJWtQ3SKbapo/G7B+chgXzI1gENdkT1KeZsitKVvkkK80UdQ dHDap8pRdZ/C97ExFc7P776UN0xe0NUoXYvpq9eF1Di8g3tCYgtRaGmrvvBq6q11Qzg+ VZiw== 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=g1uKi5sOt1fH6YVnJUMSYoSlVHQsQeCmX7nOP4zSUY4=; b=i5yfjJ01GsAkoUhXkwEibtWVtC7/r6hHo7JgEwHbE53+cfMxCeuGKr55dae/xL/rXD CeyhkeeiUicEcitFq8dGNXWbjWL4zSy2xvLQEVU3eMs1A7rTmza4ZAn6LFAx3GOQJz1q vaoDOXyhEMypVdXEoEPjYeNwfTFGDFK71slADpul3BSHvqN0sHMGVXdc9ai8YT9d5lkf wrTrq/Y+NfMlgYJBXeFMl0vMATynpOMD1sH/GrFG5l67SMhuzjAbaSnq+Q3GRieI+oon cVmxXFe3R37rHOkX5bk5Vjro5oyvwmS8d7AavlfU9mkZIxoFOYXySOM8DCBadICB8wAu /bCA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="L/40VUqa"; 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 d21si21542540pfj.98.2019.02.21.06.39.00; Thu, 21 Feb 2019 06:39:15 -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="L/40VUqa"; 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 S1728538AbfBUOh5 (ORCPT + 99 others); Thu, 21 Feb 2019 09:37:57 -0500 Received: from mail.kernel.org ([198.145.29.99]:59362 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728492AbfBUOhy (ORCPT ); Thu, 21 Feb 2019 09:37:54 -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 360A92075C; Thu, 21 Feb 2019 14:37:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550759873; bh=HxZG9l8KvI1W4a3dp/yYKV1Wm48qUbbKN2WDQYRkkHU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=L/40VUqa/smMOgFvSePoASdUfyNKtDWM/iOOeW04TeajbqdoGAuJp0ohf7iWhkE5z sUnYEeN6XCvfYjL1ubfqV1nVhTYJY+7GVx8Wrw7Ol/3246iAF6iMXcPSrH7R2p0QAL I7nbLcQXJ+PUkddkduGu7hwJumEi5sfH3i10A/SY= 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.4 02/20] vsock: cope with memory allocation failure at socket creation time Date: Thu, 21 Feb 2019 15:35:32 +0100 Message-Id: <20190221141946.847448508@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190221141946.772985220@linuxfoundation.org> References: <20190221141946.772985220@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.4-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 d24773552b641..217810674c358 100644 --- a/net/vmw_vsock/vmci_transport.c +++ b/net/vmw_vsock/vmci_transport.c @@ -1656,6 +1656,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