https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 16:08:39 +0000 https://db.gcve.eu/vuln/cve-2022-50058 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vdpa_sim_blk: set number of address spaces and virtqueue groups</p> <p>Commit bda324fd037a (&#34;vdpasim: control virtqueue support&#34;) added two new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to initialize them for vdpa_sim_blk.</p> <p>When creating a new vdpa_sim_blk device this causes the kernel to panic in this way:    $ vdpa dev add mgmtdev vdpasim_blk name blk0    BUG: kernel NULL pointer dereference, address: 0000000000000030    ...    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]    ...    Call Trace:     &lt;TASK&gt;     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]     vdpasim_map_range+0x91/0xd0 [vdpa_sim]     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]     ...</p> <p>This happens because vdpasim-&gt;iommu[0] is not initialized when dev_attr.nas is 0.</p> <p>Let&#39;s fix this issue by initializing both (nas, ngroups) to 1 for vdpa_sim_blk.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>vdpa_sim_blk: set number of address spaces and virtqueue groups</p> <p>Commit bda324fd037a (&#34;vdpasim: control virtqueue support&#34;) added two new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to initialize them for vdpa_sim_blk.</p> <p>When creating a new vdpa_sim_blk device this causes the kernel to panic in this way:    $ vdpa dev add mgmtdev vdpasim_blk name blk0    BUG: kernel NULL pointer dereference, address: 0000000000000030    ...    RIP: 0010:vhost_iotlb_add_range_ctx+0x41/0x220 [vhost_iotlb]    ...    Call Trace:     &lt;TASK&gt;     vhost_iotlb_add_range+0x11/0x800 [vhost_iotlb]     vdpasim_map_range+0x91/0xd0 [vdpa_sim]     vdpasim_alloc_coherent+0x56/0x90 [vdpa_sim]     ...</p> <p>This happens because vdpasim-&gt;iommu[0] is not initialized when dev_attr.nas is 0.</p> <p>Let&#39;s fix this issue by initializing both (nas, ngroups) to 1 for vdpa_sim_blk.</p> https://db.gcve.eu/vuln/cve-2022-50058