LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects virtual socket traffic used by some VM host-guest communication paths. Large file transfers over SFTP-over-vsock can trigger kernel memory allocation failures. The public record does not provide CVSS, CWE, or confirmed business impact, so urgency depends on whether affected systems use vhost/vsock.

Executive priority

Treat this as a targeted Linux virtualization maintenance item, not a broad emergency from current evidence. Prioritize patch confirmation on virtualization hosts and platforms relying on vsock file transfer, especially where availability issues have been observed.

Technical view

In vhost/vsock transmit handling, large packets around 32 kB used kmalloc, which can fail under allocation pressure because it needs higher-order contiguous pages. Kernel stable fixes switch the allocation/free path to kvmalloc/kvfree, which can fall back to vmalloc for larger allocations.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with vhost_vsock enabled for VM or sandbox host-guest communication. General Linux servers that do not use vsock or vhost_vsock appear less likely exposed, based only on the provided record.

Exploitation context

The source bundle describes allocation failures during large SFTP-over-vsock transfers. It does not cite active exploitation, public exploit code, KEV listing, privilege requirements, or a demonstrated crash path beyond kernel allocation failure logs.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. No CVSS, CWE, exploit status, or full impact statement is provided. The fix changes allocation strategy, suggesting an availability or reliability issue tied to memory allocation behavior.

Mitigation direction

  • Identify Linux kernels using vhost_vsock or vsock-based host-guest communication.
  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported CVE-2022-50271 fixes.
  • Prioritize virtualization hosts or platforms that support SFTP-over-vsock file transfer.
  • Monitor kernel logs for vhost_vsock page allocation failures until patched.

Validation and detection

  • Inventory kernel versions against vendor advisories and the CVE record.
  • Confirm whether vhost_vsock is loaded or required on each host.
  • Verify patched kernels include the kvmalloc/kvfree stable commit for this issue.
  • Review logs for repeated vhost_vsock allocation failure messages.
  • Document systems where vsock is unused as lower priority.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50271 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8, 433fc58e6bf2c8bd97e57153ed28e64fd78207b8unaffected
LinuxLinux4.8, 0, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.