CVE-2022-50271
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.8 (inc) to 4.14.296 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.262 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.220 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.150 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 5.19.17 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.0.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's vhost/vsock component occurs because the kernel's memory allocator (kmalloc) fails when trying to allocate large memory regions (such as 32kB packets) needed during data transfer over vsock, like when copying large files over sftp. The failure leads to page allocation errors. The fix involves using kvmalloc/kvfree, which better handles larger memory allocations.
How can this vulnerability impact me? :
This vulnerability can cause failures in memory allocation during large data transfers over vsock, potentially leading to errors or crashes in the affected Linux kernel component. This could disrupt data transfer operations such as sftp over vsock, impacting system stability or performance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for page allocation failures related to vhost/vsock, specifically messages indicating kmalloc failures when handling large packets (around 32kB). You can check the kernel log using commands like 'dmesg | grep vhost_vsock' or 'journalctl -k | grep vhost_vsock' to look for error traces similar to the provided call trace involving kmalloc failures.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to apply the fix that replaces kmalloc with kvmalloc/kvfree for larger packets in the vhost/vsock code. This workaround addresses the page allocation failure by using kvmalloc instead of kmalloc for large memory allocations.