CVE-2022-50263: vdpasim: fix memory leak when freeing IOTLBs
In the Linux kernel, the following vulnerability has been resolved:
vdpasim: fix memory leak when freeing IOTLBs
After commit bda324fd037a ("vdpasim: control virtqueue support"),
vdpasim->iommu became an array of IOTLB, so we should clean the
mappings of each free one by one instead of just deleting the ranges
in the first IOTLB which may leak maps.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the vDPA simulator path. When IOTLB mappings are freed, only the first table may be cleaned, leaving others allocated. The business risk is uncertain because no CVSS score, exploitation evidence, or impact detail is provided.
Executive priority
Handle through normal kernel maintenance unless internal exposure to vdpasim is confirmed. Escalate priority for virtualization platforms or hosts where resource leaks could affect service availability.
Technical view
After Linux commit bda324fd037a added vdpasim control virtqueue support, vdpasim->iommu became an array of IOTLBs. The vulnerable cleanup path deleted ranges only from the first IOTLB, potentially leaking mappings from the remaining entries.
Likely exposure
Exposure appears limited to Linux systems using or carrying the vdpasim/vDPA simulator code on affected kernel versions listed in the CVE source, including 5.19, 6.0.19, 6.1.5, and 6.2. Product and distribution mappings are not provided.
Exploitation context
The source bundle does not report active exploitation, KEV listing, public exploit use, or a defined attack path. Treat this as a kernel resource-management flaw with incomplete public risk evidence, not as a confirmed exploited issue.
Researcher notes
The record is narrow: a resolved Linux kernel memory leak with three stable commit references, no CVSS, no CWE, and no exploit signal. Avoid assuming privilege boundaries or denial-of-service reachability without vendor or code-path confirmation.
Mitigation direction
Check Linux vendor guidance for affected distribution kernels.
Update to a kernel package containing the referenced stable fixes.
Prioritize systems that use vDPA, vhost, virtualization, or kernel simulator features.
If unused, consider disabling unavailable vdpasim-related functionality per vendor guidance.
Validation and detection
Inventory Linux kernel versions across hosts and images.
Identify systems where vdpasim or related vDPA functionality is present.
Compare kernel package changelogs against the referenced stable commit IDs.
Track vendor advisories because CVSS and distribution impact are not supplied.
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-50263 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Sep 15, 2025, 14:20 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.