Answer in brief
CVE-2026-93827 records a High severity (CVSS 8.4) vulnerability in virtio-fs: avoid double-free on failed queue setup. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <20ef4739b329bb09cff11dd2458795a50674658e || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6af3330ec5d5fb8c06c04eb520a71cf73ea5a765 || >=0 <6.12.111 || >=0 <6.18.53 | 3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad, 20ef4739b329bb09cff11dd2458795a50674658e, 6af3330ec5d5fb8c06c04eb520a71cf73ea5a765, 6.12.111, 6.18.53 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.