CVE-2022-50271

  • Published: 2025-09-15T15:15:37.930

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:
[] dump_stack+0x97/0xdb
[] warn_alloc_failed+0x10f/0x138
[] ? __alloc_pages_direct_compact+0x38/0xc8
[] __alloc_pages_nodemask+0x84c/0x90d
[] alloc_kmem_pages+0x17/0x19
[] kmalloc_order_trace+0x2b/0xdb
[] __kmalloc+0x177/0x1f7
[] ? copy_from_iter+0x8d/0x31d
[] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
[] vhost_worker+0xf7/0x157 [vhost]
[] kthread+0xfd/0x105
[] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
[] ? flush_kthread_worker+0xf3/0xf3
[] ret_from_fork+0x4e/0x80
[] ? flush_kthread_worker+0xf3/0xf3

Work around by doing kvmalloc instead.

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2022-50271

CVE-2022-50271 is a unknown severity vulnerability affecting the affected product.

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: [] dump_stack+0x97/0xdb [] warn_alloc_failed+0x10f/0x138 [] […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

HARD
⏱️ Time to Exploit: > 4 hours
🛠️ Skills Required: Advanced security expertise
💰 Public Exploits: Rare or not public

Vulnerability Timeline

Sep 15, 2025
Vulnerability Published

CVE details first published to NVD database

Nov 12, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.