CVE-2026-93827
HighIn 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.
CVSS 3.1 score
8.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected versions
Linux kernel versions
6.9
and later are affected. Fixed in
6.12.111,
6.18.53,
7.2
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-93827?
CVE-2026-93827 is a High severity Linux kernel vulnerability with a CVSS score of 8.4 out of 10 . It affects Linux kernel versions from 6.9 onward and has been patched in 6.12.111, 6.18.53 and 7.2. CVE-2026-93827 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-93827?
CVE-2026-93827 has a CVSS score of 8.4 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2026-93827?
Yes. CVE-2026-93827 has been patched. Fixed versions include 6.12.111, 6.18.53 and 7.2. If you are running Linux kernel 6.9 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-93827 actively exploited?
No. CVE-2026-93827 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.