CVE-2026-93827

Description

A flaw was found in the Linux kernel's virtio-fs file system driver. When queue initialization fails—such as when a device advertises more request queues than supported—the driver fails to clear memory pointers after releasing them, resulting in a double-free condition during error cleanup. An attacker capable of presenting a malformed virtio-fs device can exploit this flaw to cause memory corruption, leading to a system crash and Denial of Service (DoS).

Statement

A double free in the virtio fs probe failure path occurs because virtio_fs_setup_vqs frees fs vqs and fs mq_map after virtio_find_vqs fails but leaves the pointers non NULL. Later probe cleanup drops the final kobject reference and virtio_fs_ktype_release frees the same allocations again, creating a kernel memory corruption condition. A malicious or malformed virtio fs device can trigger the failure by advertising more request queues than the transport provides. The attack vector is adjacent AV:A because the attacker must control a virtio device or virtual machine device configuration and it is not a network protocol attack. For the CVSS the PR:N because no guest user account or local code execution is required when an attacker controls the presented virtio device. Impact is at least guest kernel denial of service and may include confidentiality and integrity impact through double free based memory corruption.

Mitigation

To mitigate this vulnerability, prevent the virtiofs kernel module from loading on the system if virtio-fs shared filesystems are not required.

1. Add a configuration rule to disable autoloading of the module:
# echo "install virtiofs /bin/true" > /etc/modprobe.d/disable-virtiofs.conf

2. If the module is currently loaded, unload it:
# modprobe -r virtiofs

Warning: If virtiofs is in active use by mounted filesystems, unloading the module will fail. A system reboot may be required to completely unload the driver and ensure configuration changes take effect.

Caveats: Disabling the virtiofs module prevents the guest system from mounting filesystems shared via virtio-fs from the hypervisor.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.5N/A8.4
Attack VectorAdjacent NetworkN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/AHigh
Integrity ImpactNoneN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.