Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system when a vDPA simulator block device is created. It is narrow in scope: the public record describes a kernel panic tied to vdpa_sim_blk initialization, not remote compromise or data theft.
Executive priority
Prioritize according to vDPA simulator use. For most production fleets this is likely routine kernel maintenance; for hosts where untrusted users can manage vDPA devices, handle sooner as an availability risk.
Technical view
vdpa_sim_blk failed to initialize vdpasim_dev_attr fields nas and ngroups after control virtqueue support added them. With nas set to 0, vdpasim->iommu[0] is missing, leading to a NULL pointer dereference in vhost_iotlb_add_range_ctx during device creation.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or affected commits where vdpa_sim_blk can be used. Highest relevance is virtualization, lab, CI, or development hosts using vDPA simulator block devices.
Exploitation context
The sources do not report active exploitation, and this CVE is not listed as KEV in the provided bundle. The described impact is a local kernel panic triggered during creation of a new vdpa_sim_blk device.
Researcher notes
The public data is sparse: no CVSS, CWE, exploit report, or detailed vendor matrix is provided. The root cause and crash path are clear from the kernel description, but environmental prerequisites are not fully documented.
Mitigation direction
- Update to a kernel package containing the referenced stable fixes.
- Check Linux distribution advisories for backported fixes and supported versions.
- Restrict vDPA device management to trusted administrators only.
- Avoid creating vdpa_sim_blk devices on affected kernels until fixed.
Validation and detection
- Inventory Linux kernel versions against the affected ranges in the CVE record.
- Check whether vdpa_sim_blk or vDPA simulator functionality is present or used.
- Confirm fixed commits appear in kernel source, package changelog, or vendor advisory.
- Review crash logs for vhost_iotlb or vdpasim NULL pointer dereferences.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2022-50058 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
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.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/a291c7d289fac2cb13fb2614a9a251afbbd86ce9CVE reference, Linux
- https://git.kernel.org/stable/c/19cd4a5471b8eaa4bd161b0fdb4567f2fc88d809CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.