In the Linux kernel, the following vulnerability has been resolved: virtio_pci: fix vq info pointer lookup via wrong index Unbinding a vir

In the Linux kernel, the following vulnerability has been resolved:

virtio_pci: fix vq info pointer lookup via wrong index

Unbinding a virtio balloon device:

 1echo virtio0 > /sys/bus/virtio/drivers/virtio_balloon/unbind

triggers a NULL pointer dereference. The dmesg says:

 1BUG: kernel NULL pointer dereference, address: 0000000000000008
 2[...]
 3RIP: 0010:__list_del_entry_valid_or_report+0x5/0xf0
 4Call Trace:
 5<TASK>
 6vp_del_vqs+0x121/0x230
 7remove_common+0x135/0x150
 8virtballoon_remove+0xee/0x100
 9virtio_dev_remove+0x3b/0x80
10device_release_driver_internal+0x187/0x2c0
11unbind_store+0xb9/0xe0
12kernfs_fop_write_iter.llvm.11660790530567441834+0xf6/0x180
13vfs_write+0x2a9/0x3b0
14ksys_write+0x5c/0xd0
15do_syscall_64+0x54/0x230
16entry_SYSCALL_64_after_hwframe+0x29/0x31
17[...]
18</TASK>

The virtio_balloon device registers 5 queues (inflate, deflate, stats,
free_page, reporting) but only the first two are unconditional. The
stats, free_page and reporting queues are each conditional on their
respective feature bits. When any of these features are absent, the
corresponding vqs_info entry has name == NULL, creating holes in the
array.

The root cause is an indexing mismatch introduced when vq info storage
was changed to be passed as an argument. vp_find_vqs_msix() and
vp_find_vqs_intx() store the info pointer at vp_dev->vqs[i], where 'i'
is the caller's sparse array index. However, the virtqueue itself gets
vq->index assigned from queue_idx, a dense index that skips NULL
entries. When holes exist, 'i' and queue_idx diverge. Later,
vp_del_vqs() looks up info via vp_dev->vqs[vq->index] using the dense
index into the sparsely-populated array, and hits NULL.

Fix this by storing info at vp_dev->vqs[queue_idx] instead of
vp_dev->vqs[i], so the store index matches the lookup index
(vq->index). Apply the fix to both the MSIX and INTX paths.