LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50738: vhost-vdpa: fix an iotlb memory leak

In the Linux kernel, the following vulnerability has been resolved: vhost-vdpa: fix an iotlb memory leak Before commit 3d5698793897 ("vhost-vdpa: introduce asid based IOTLB") we called vhost_vdpa_iotlb_unmap(v, iotlb, 0ULL, 0ULL - 1) during release to free all the resources allocated when processing user IOTLB messages through vhost_vdpa_process_iotlb_update(). That commit changed the handling of IOTLB a bit, and we accidentally removed some code called during the release. We partially fixed this with commit 037d4305569a ("vhost-vdpa: call vhost_vdpa_cleanup during the release") but a potential memory leak is still there as showed by kmemleak if the application does not send VHOST_IOTLB_INVALIDATE or crashes: unreferenced object 0xffff888007fbaa30 (size 16): comm "blkio-bench", pid 914, jiffies 4294993521 (age 885.500s) hex dump (first 16 bytes): 40 73 41 07 80 88 ff ff 00 00 00 00 00 00 00 00 @sA............. backtrace: [<0000000087736d2a>] kmem_cache_alloc_trace+0x142/0x1c0 [<0000000060740f50>] vhost_vdpa_process_iotlb_msg+0x68c/0x901 [vhost_vdpa] [<0000000083e8e205>] vhost_chr_write_iter+0xc0/0x4a0 [vhost] [<000000008f2f414a>] vhost_vdpa_chr_write_iter+0x18/0x20 [vhost_vdpa] [<00000000de1cd4a0>] vfs_write+0x216/0x4b0 [<00000000a2850200>] ksys_write+0x71/0xf0 [<00000000de8e720b>] __x64_sys_write+0x19/0x20 [<0000000018b12cbb>] do_syscall_64+0x3f/0x90 [<00000000986ec465>] entry_SYSCALL_64_after_hwframe+0x63/0xcd Let's fix this calling vhost_vdpa_iotlb_unmap() on the whole range in vhost_vdpa_remove_as(). We move that call before vhost_dev_cleanup() since we need a valid v->vdev.mm in vhost_vdpa_pa_unmap(). vhost_iotlb_reset() call can be removed, since vhost_vdpa_iotlb_unmap() on the whole range removes all the entries. The kmemleak log reported was observed with a vDPA device that has `use_va` set to true (e.g. VDUSE). This patch has been tested with both types of devices.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50738 is a Linux kernel memory leak in vhost-vdpa cleanup. If an application using this interface fails to invalidate mappings or crashes, kernel memory may not be freed. The main business concern is reliability degradation on hosts using vDPA/VDUSE-style virtualization or I/O acceleration features.

Executive priority

Treat as a targeted reliability patch for specialized Linux virtualization or I/O hosts. It is not currently supported by public evidence of active exploitation, but affected infrastructure should be updated during normal security maintenance, sooner for high-density or memory-sensitive platforms.

Technical view

The issue is in Linux kernel vhost-vdpa IOTLB handling after ASID-based IOTLB changes. Cleanup no longer fully released IOTLB entries created from user IOTLB updates. The fix calls vhost_vdpa_iotlb_unmap() across the full range during address-space removal before vhost_dev_cleanup().

Likely exposure

Exposure is likely limited to Linux systems using vhost-vdpa, vDPA, or VDUSE-related devices. General Linux servers not using these kernel facilities are less likely to be affected. The provided data lists Linux kernel versions including 5.19, 6.0.19, 6.1.5, and 6.2 as affected entries, but version applicability should be confirmed with vendor advisories.

Exploitation context

No CISA KEV listing or source evidence of active exploitation is provided. The described trigger is an application that does not send VHOST_IOTLB_INVALIDATE or crashes, leaving allocations unreferenced. The practical impact appears to be memory leakage rather than direct code execution.

Researcher notes

The source describes kmemleak output from blkio-bench and notes testing with devices where use_va is true, such as VDUSE, and with both device types. Severity, CVSS, and CWE are not provided, so impact assessment remains bounded by the published kernel description.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Prioritize hosts using vhost-vdpa, vDPA, or VDUSE workloads.
  • Check your Linux distribution or appliance vendor guidance for backported fixes.
  • Plan maintenance for virtualization or I/O acceleration hosts if affected.

Validation and detection

  • Inventory Linux hosts using vhost-vdpa, vDPA, or VDUSE.
  • Compare running kernel builds against vendor-fixed kernel advisories.
  • Review kernel package changelogs for the referenced vhost-vdpa IOTLB cleanup fix.
  • Monitor affected hosts for unexplained kernel memory growth during relevant workloads.
Prepared
Confidence
medium
Sources
5

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-50738 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
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3d5698793897a2b9c0060d899881d1a0591630d5, 3d5698793897a2b9c0060d899881d1a0591630d5, 3d5698793897a2b9c0060d899881d1a0591630d5unaffected
LinuxLinux5.19, 0, 6.0.19, 6.1.5, 6.2affected
Weakness

CWE details

No CWE listed

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