Linux
virtio-fs: avoid double-free on failed queue setup
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 and mitigation
From the CVE record and the vendor's references.Affected
- >= a8f62f50b4e4ea92a938fca2ec1bd108d7f210e9, < 3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad
- >= a8f62f50b4e4ea92a938fca2ec1bd108d7f210e9, < 20ef4739b329bb09cff11dd2458795a50674658e
- >= a8f62f50b4e4ea92a938fca2ec1bd108d7f210e9, < 6af3330ec5d5fb8c06c04eb520a71cf73ea5a765
Fixed in 3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad, 20ef4739b329bb09cff11dd2458795a50674658e, 6af3330ec5d5fb8c06c04eb520a71cf73ea5a765
- 6.9
Fixed in 0, 6.12.111, 6.18.53, 7.2
Mitigation
Upgrade Linux to 3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad or 20ef4739b329bb09cff11dd2458795a50674658e or 6af3330ec5d5fb8c06c04eb520a71cf73ea5a765 or later.
Upgrade Linux to 0 or 6.12.111 or 6.18.53 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.