---
id: CVE-2026-93827
title: |-
  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()
summary: |-
  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,…
severity: high
cvss: 8.4
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    20ef4739b329bb09cff11dd2458795a50674658e
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    6af3330ec5d5fb8c06c04eb520a71cf73ea5a765
  - Linux < 6.12.111
  - Linux < 6.18.53
  - Linux (all versions)
published: '2026-09-24'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T13:17:23.513'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-93827'
references:
  - url: 'https://git.kernel.org/stable/c/20ef4739b329bb09cff11dd2458795a50674658e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/6af3330ec5d5fb8c06c04eb520a71cf73ea5a765'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-24T16:47:15.890Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.