linux-cve-announce - CVE-2022-50271: vhost/vsock: Use kvmalloc/kvfree for larger packets.

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: <2025091505-CVE-2022-50271-2175@gregkh>
Date: Mon, 15 Sep 2025 16:21:13 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50271: vhost/vsock: Use kvmalloc/kvfree for larger packets.

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

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

vhost/vsock: Use kvmalloc/kvfree for larger packets.

When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.

 vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [<ffffffffb6a0df64>] dump_stack+0x97/0xdb
  [<ffffffffb68d6aed>] warn_alloc_failed+0x10f/0x138
  [<ffffffffb68d868a>] ? __alloc_pages_direct_compact+0x38/0xc8
  [<ffffffffb664619f>] __alloc_pages_nodemask+0x84c/0x90d
  [<ffffffffb6646e56>] alloc_kmem_pages+0x17/0x19
  [<ffffffffb6653a26>] kmalloc_order_trace+0x2b/0xdb
  [<ffffffffb66682f3>] __kmalloc+0x177/0x1f7
  [<ffffffffb66e0d94>] ? copy_from_iter+0x8d/0x31d
  [<ffffffffc0689ab7>] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [<ffffffffc06828d9>] vhost_worker+0xf7/0x157 [vhost]
  [<ffffffffb683ddce>] kthread+0xfd/0x105
  [<ffffffffc06827e2>] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [<ffffffffb683dcd1>] ? flush_kthread_worker+0xf3/0xf3
  [<ffffffffb6eb332e>] ret_from_fork+0x4e/0x80
  [<ffffffffb683dcd1>] ? flush_kthread_worker+0xf3/0xf3

Work around by doing kvmalloc instead.

The Linux kernel CVE team has assigned CVE-2022-50271 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 4.14.296 with commit 0d720c3f0a03e97867deab7e480ba3d3e19837ba
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 4.19.262 with commit 7aac8c63f604e6a6a46560c0f0188cd0332cf320
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 5.4.220 with commit e6d0152c95108651f1880c1ddfab47cb9e3e62d0
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 5.10.150 with commit b4a5905fd2ef841cd61e969ea692c213c2e5c1f7
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 5.15.75 with commit e28a4e7f0296824c61a81e7fd54ab48bad3e75ad
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 5.19.17 with commit a99fc6d818161d6f1ff3307de8bf5237f6cc34d8
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 6.0.3 with commit 36c9f340c60413e28f980c0224c4e9d35851526b
	Issue introduced in 4.8 with commit 433fc58e6bf2c8bd97e57153ed28e64fd78207b8 and fixed in 6.1 with commit 0e3f72931fc47bb81686020cc643cde5d9cd0bb8

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-50271
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/vhost/vsock.c
	net/vmw_vsock/virtio_transport_common.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/0d720c3f0a03e97867deab7e480ba3d3e19837ba
	https://git.kernel.org/stable/c/7aac8c63f604e6a6a46560c0f0188cd0332cf320
	https://git.kernel.org/stable/c/e6d0152c95108651f1880c1ddfab47cb9e3e62d0
	https://git.kernel.org/stable/c/b4a5905fd2ef841cd61e969ea692c213c2e5c1f7
	https://git.kernel.org/stable/c/e28a4e7f0296824c61a81e7fd54ab48bad3e75ad
	https://git.kernel.org/stable/c/a99fc6d818161d6f1ff3307de8bf5237f6cc34d8
	https://git.kernel.org/stable/c/36c9f340c60413e28f980c0224c4e9d35851526b
	https://git.kernel.org/stable/c/0e3f72931fc47bb81686020cc643cde5d9cd0bb8