Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp549691imp; Thu, 21 Feb 2019 06:40:13 -0800 (PST) X-Google-Smtp-Source: AHgI3IZCHjx8pZ0O5PQdFGcbVFq9jwMTdznQumJMEHsYpSLk2jt5A44QrT6ZyEmdMu9fjEmxrcd7 X-Received: by 2002:a17:902:f64:: with SMTP id 91mr42899790ply.132.1550760013373; Thu, 21 Feb 2019 06:40:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550760013; cv=none; d=google.com; s=arc-20160816; b=bB5vC6hoHvJufrEB5yneh9PxpKha04NJtfGPbrLCXE84cTUKalqbjR9owZgfsPdNy0 YMmRnNvw3x6pU1AOgj5EyrrAO6XzW5GfoLFjtm84fcRsqGGOnRc+qWTRh52RoxjQ56pH hXI8PYM7VxqOrk0rn6piSAtNID/Y1EpUVNPAW184pUlOtfEEKs++TnqviFHZR1C/0Z6O 2rJvJZygw+1GlnDG5KAyyYrv8t2PW1zel+wliuQ1vGsnsTbPERQmgpNcrVwfR9lunL7J 9GLYDXpBl+daYMMDc5LnA7ZFg76t9L6bXCU9vZsNxxfqstkWmedXAfth+t9a06lWqkom 1FIQ== 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=xPat8Upi+JblkfMhyvad6QZQy2EvUGAW8XAjPrM2ysY=; b=ByezEmLfigjLIjERy+P4Eu62oeLEj+J142yOBpagRPdGr7kP9GdAwJ+dLwHHnKc4Ue gCphy2KL1foPw5e5XgfWQajK5iHso2psB9ocDCerXxmGAXIRzXaIE/Xa2C0V4Fm/aU56 Tp4v/f6xts0HbW0su+tXgEGZe97n9UistOwLQfgDpg4hqTQDqtijx/dInJbYzFjkxKV3 e9iOtdjSGv+4hwY8q6UIUZn5cOneavZqb9lXKea4iZfdxpPYUPDN/LqClDDpCsspo7Kw AVSF4TABym9l5AQ/R/VztCjOXIBtijdbqUOGNwBC8shx+iX7CI9qrJbRlfoFo63NZJ85 zUTw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=cj844Eah; 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 64si22630424pld.436.2019.02.21.06.39.58; Thu, 21 Feb 2019 06:40:13 -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=cj844Eah; 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 S1728746AbfBUOir (ORCPT + 99 others); Thu, 21 Feb 2019 09:38:47 -0500 Received: from mail.kernel.org ([198.145.29.99]:60576 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728730AbfBUOin (ORCPT ); Thu, 21 Feb 2019 09:38:43 -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 6CDBC2075C; Thu, 21 Feb 2019 14:38:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550759922; bh=MSvEcePaKHMHRAxUB9RmjY27z6mxbEltGZqIhEibSIk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=cj844EahT6fXFvRLCdogZYzG1B+YrRXJRFrsPF9+rzBIWfsSIzfBTzKgVI8LxyvnM 8AfVqOqFUiGghv0bXEHKWwL6uOHTAHKHgkcvTQsdKm6A4cRAbexWuEzMrD8ognbm9N Ol9j/eGPyBN0wM/KBYxjMCbCJh0z9xKuHojvmh0A= 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.9 02/20] vsock: cope with memory allocation failure at socket creation time Date: Thu, 21 Feb 2019 15:35:40 +0100 Message-Id: <20190221125242.548927197@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190221125242.153179182@linuxfoundation.org> References: <20190221125242.153179182@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.9-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 008f3424dcbce..102bf9194662c 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