linux-cve-announce - CVE-2022-50842: drm/virtio: Check whether transferred 2D BO is shmem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025123020-CVE-2022-50842-e43a@gregkh>
Date: Tue, 30 Dec 2025 13:13:28 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50842: drm/virtio: Check whether transferred 2D BO is shmem

From: Greg Kroah-Hartman <gregkh@...nel.org>

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