Linux vulnerability

What happened

In the Linux kernel, the following vulnerability has been resolved: virtio-fs: avoid double-free on failed queue setup virtio_fs_setup_vqs() allocates fs->vqs and fs->mq_map before calling virtio_find_vqs(). If virtio_find_vqs() fails, the error path frees both pointers and returns an error to virtio_fs_probe(). virtio_fs_probe() then drops the last kobject reference, and virtio_fs_ktype_release() frees fs->vqs and fs->mq_map again. This leaves dangling pointers in struct virtio_fs and can trigger a double-free during probe failure cleanup. Set fs->vqs and fs->mq_map to NULL immediately after kfree() in the virtio_fs_setup_vqs() error path so that the later kobject release sees an uninitialized state and kfree(NULL) becomes harmless. This can be reproduced when a broken virtio-fs device advertises more request queues than the transport actually provides. In that case virtio_find_vqs() fails while setting up the extra queue, and the probe path reaches the double-free cleanup sequence.

Affected versions

Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 20ef4739b329bb09cff11dd2458795a50674658e (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 6af3330ec5d5fb8c06c04eb520a71cf73ea5a765 (git); before 6.12.111 (semver); before 6.18.53 (semver) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.