From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DC0783E6399 for ; Sat, 15 Aug 2026 12:28:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786796896; cv=none; b=gFhJ8h5peLryklEbyCk1BL7g8uI6r33+WSp1s/X3vnFKjfazBsEt6jgSG2GycrldeD4J5p4LNgTJ58JMY2PyzWdnhdP1X1vYhXiRtCkxRseI6ZL96ApNx7BRxAQTV/f4sS1asOuOg0jTJK9MtGfzJW+TZUsDvmb401/5DnKvR68= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786796896; c=relaxed/simple; bh=RnwCps15zN3jew4Bblp3k9cUWcW3gfZylxz+mY5STfc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=rCf7yCFaBXeWRuv1bwsdQtcbgBk8f0jApsyZIfT7yKjewTWcUGBoHtuidYoId40COoIjS+WpC5KFSHV8yg/xsuFTW/+kKp4dTLeD5qUpzp2uopS5gOn5PvF+stRbwsknw87oAhU/kqHXxkIYV0PJ8cwgTAbCsXY734k+0SmYEVA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=bDsnogHm; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="bDsnogHm" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0925C1F000E9; Sat, 15 Aug 2026 12:28:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786796894; bh=D0/ffk+D2iz9zjiwsvzWcKyM1MjsTeI17WKPp0RFtCQ=; h=From:To:Cc:Subject:Date:Reply-To; b=bDsnogHmn9BHRrHEBGOYZTu8EgVvRiKM8HionYrA3vbQceRAHDl6+fbMHRcGpTacl CRREZNhTckFIATkG4SrB9i4ox4N8fYG+j0GozOnnMNKUs0tMvWws0tsNBBkPDdM9Bz MKGl9Qt4/vK/yxkJcZwYCgZhSXWTdfv0xAtRzYSs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74442: drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure Date: Sat, 15 Aug 2026 21:25:23 +0900 Message-ID: <2026081529-CVE-2026-74442-922b@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3155; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=9jvrnF8GWLRAM+I78FwgE7DFjMvLO0pwk1fQyXeF2/o=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNUTs5cloOn3N8sfve45R7xv/NblqGv68zZKxfGvE/f 9/7hwcyO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiSQcY5ufdX/+gN9V4tp25 lZqp5BKRy3FvJRjmF7V5xL9OzHq5/LliVg0LX0qXmoYEAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure Two paths through vmw_vkms_init() can leave vmw->crc_workq NULL while still leaving the rest of the driver in a state that calls vmw_vkms_cleanup() at module unload: 1. vmw_host_get_guestinfo(GUESTINFO_VBLANK, ...) failing or returning an oversized buffer -- the common case on hosts without a VBLANK guestinfo entry -- early-returned before the workqueue allocation. 2. alloc_ordered_workqueue() returning NULL on memory pressure. vmw_vkms_cleanup() then calls destroy_workqueue(NULL), which dereferences wq->name and panics. Fix the first case by removing the early return: vmw->vkms_enabled is already false on the rpci-failure path so no work will ever be queued, and allocating the workqueue unconditionally keeps the control flow simple. Fix the second case by guarding the cleanup with a NULL check, since alloc_ordered_workqueue() can still fail under low memory. The Linux kernel CVE team has assigned CVE-2026-74442 to this issue. Affected and fixed versions =========================== Issue introduced in 6.10 with commit 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 and fixed in 6.12.103 with commit 7c701778c6a369769992614dac8dc00c8ac72afc Issue introduced in 6.10 with commit 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 and fixed in 6.18.44 with commit 96efee36453b697ccbaf75091b7a1807c11809dd Issue introduced in 6.10 with commit 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 and fixed in 7.1.8 with commit 0ee0532f1d405d37f38c44cbba87342e63d3bbd4 Issue introduced in 6.10 with commit 7b0062036c3b71b4a69e244ecf0502c06c4cf5f0 and fixed in 7.2-rc6 with commit 05eaa887e7b4f40fba425f8a1d7a5a8a043092a6 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-74442 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/7c701778c6a369769992614dac8dc00c8ac72afc https://git.kernel.org/stable/c/96efee36453b697ccbaf75091b7a1807c11809dd https://git.kernel.org/stable/c/0ee0532f1d405d37f38c44cbba87342e63d3bbd4 https://git.kernel.org/stable/c/05eaa887e7b4f40fba425f8a1d7a5a8a043092a6