From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 B8BB42D73AD for ; Tue, 30 Dec 2025 12:14:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767096849; cv=none; b=ehS57gmYvEclbzsvm8L82c1KnV0Za2zC3e5I6T1CP6jHGLDYQDqarltFy/icvAGRP16yu5/NiCl7kSsvxG74RosX4VMkiF2GAu2M0CtzV4Gx2299Cf0fqNHiLQ23Adu59a5LE8Uo0Qvl7rBfnFn6bos0UNAPyvXDI3w70i9J/M0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767096849; c=relaxed/simple; bh=ntXXUZjpawrzHSDT/erefKJtnvxln/nK4OhYF/L52Ss=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ufCnerPwSVcAotyDEJ5ZDah7ScdzzfqNn945bCFw4Ky4yvWMZXsRZlppuDe12A8YaGeC+fN9llhZV1iBkQAqWbHOAhFB1VBPP/DYg+iGq42vEFgHoy8cWMuOAD5GWey+u0yE95m2DkE8F/iizfQOAZqyYQpSBnMaNHesdY2530A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=x3ZTYAc1; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="x3ZTYAc1" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 470D4C4CEFB; Tue, 30 Dec 2025 12:14:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1767096849; bh=ntXXUZjpawrzHSDT/erefKJtnvxln/nK4OhYF/L52Ss=; h=From:To:Cc:Subject:Date:Reply-To:From; b=x3ZTYAc1uGqSEzYjXxqZPVK9yMq0pzGqDNYp07000j0+q907gefWDJvWOKQ+qTVhK U/UFKq5uPeK2yju2Ex08RK1eEdRqhsofUao7IChunKUoKjR4JCJMLH9MCOEQTL+MXl 7dbHWqBlzPhEpVi5D2HtASy1pUV/KItZhILrCkYg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-50842: drm/virtio: Check whether transferred 2D BO is shmem Date: Tue, 30 Dec 2025 13:13:28 +0100 Message-ID: <2025123020-CVE-2022-50842-e43a@gregkh> X-Mailer: git-send-email 2.52.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=2170; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=j0EalBH4SaOuiOhGm4S1Lfpm3VlMGsuM6gnUuys/jZI=; b=owGbwMvMwCRo6H6F97bub03G02pJDJnBBx/YTXdlmt+ut6em2UXma+yeV4UL/yXsLz76+2rc9 /Y3nqvcOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiNosY5mfNEC/7o2TJUGDw LChIsOfMn9jN2xgWtFvu/pLrZOjWvDNJyGj/yaUFE/VYAA== 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/virtio: Check whether transferred 2D BO is shmem Transferred 2D BO always must be a shmem BO. Add check for that to prevent NULL dereference if userspace passes a VRAM BO. The Linux kernel CVE team has assigned CVE-2022-50842 to this issue. Affected and fixed versions =========================== Fixed in 5.10.150 with commit f134f261d76ae3d5ecf68db642eaa746ceb84cfb Fixed in 5.15.75 with commit f122bcb34f1a4b02ef3d95058d8fd1316ea03785 Fixed in 5.19.17 with commit 989164305b933af06d69bb91044dafbd01025371 Fixed in 6.0.3 with commit 36e133af33ea54193378b190cf92c47c12a43d34 Fixed in 6.1 with commit e473216b42aa1fd9fc6b94b608b42c210c655908 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-2022-50842 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/virtio/virtgpu_vq.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/f134f261d76ae3d5ecf68db642eaa746ceb84cfb https://git.kernel.org/stable/c/f122bcb34f1a4b02ef3d95058d8fd1316ea03785 https://git.kernel.org/stable/c/989164305b933af06d69bb91044dafbd01025371 https://git.kernel.org/stable/c/36e133af33ea54193378b190cf92c47c12a43d34 https://git.kernel.org/stable/c/e473216b42aa1fd9fc6b94b608b42c210c655908