CVE-2026-93827

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.4
EG Score
8.4HIGHhigh confidence
EG Risk
42
EG Risk 42/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

September 25, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

virtio-fs: avoid double-free on failed queue setup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6af3330ec5d5fb8c06c04eb520a71cf73ea5a765
generic

virtio-fs: avoid double-free on failed queue setup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fbc5ee776fefbc6ea34d2518f1f5f90aa2e1dad
generic

virtio-fs: avoid double-free on failed queue setup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20ef4739b329bb09cff11dd2458795a50674658e

Vendor Advisories for CVE-2026-93827(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 27× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 02:31 UTCEG score recompute
  2. 2026-10-05 02:31 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-04 13:49 UTCGHSA enrichment
  5. 2026-10-04 01:06 UTCEG score recompute
  6. 2026-10-04 01:06 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 12:22 UTCGHSA enrichment
  9. 2026-10-02 23:40 UTCEG score recompute
  10. 2026-10-02 23:40 UTCGHSA enrichment
  11. 2026-10-02 10:58 UTCGHSA enrichment
  12. 2026-10-01 22:15 UTCEG score recompute
  13. 2026-10-01 22:15 UTCGHSA enrichment
  14. 2026-10-01 19:51 UTCEPSS rescore
  15. 2026-10-01 09:32 UTCGHSA enrichment
  16. 2026-09-30 20:51 UTCEG score recompute
  17. 2026-09-30 20:51 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 08:09 UTCGHSA enrichment
  20. 2026-09-29 19:27 UTCEG score recompute
  21. 2026-09-29 19:27 UTCGHSA enrichment
  22. 2026-09-29 06:42 UTCEG score recompute
  23. 2026-09-29 06:42 UTCGHSA enrichment
  24. 2026-09-28 18:01 UTCEG score recompute
  25. 2026-09-28 18:00 UTCGHSA enrichment
Show 22 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 05:01 UTCGHSA enrichment
  4. 2026-09-27 16:18 UTCEG score recompute
  5. 2026-09-27 16:18 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 03:36 UTCEG score recompute
  8. 2026-09-27 03:36 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 14:51 UTCGHSA enrichment
  11. 2026-09-26 02:05 UTCEG score recompute
  12. 2026-09-26 02:04 UTCGHSA enrichment
  13. 2026-09-25 13:22 UTCEG score recompute
  14. 2026-09-25 13:22 UTCGHSA enrichment
  15. 2026-09-25 12:55 UTCEG score recompute
  16. 2026-09-25 12:55 UTCGHSA enrichment
  17. 2026-09-25 05:17 UTCEG score recompute▲ 8.40
  18. 2026-09-25 05:17 UTCGHSA enrichment
  19. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  20. 2026-09-24 17:33 UTCNVD update
  21. 2026-09-24 16:29 UTCEG score recompute
  22. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93827?
CVE-2026-93827 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: virtio-fs: avoid double-free on failed queue setup virtiofssetupvqs() allocates fs->vqs and fs->mqmap before calling virtiofindvqs(). If virtiofindvqs() fails, the error path frees both pointers and returns an error to…
When was CVE-2026-93827 disclosed?
CVE-2026-93827 was first published on September 24, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93827 actively exploited?
CVE-2026-93827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93827?
CVE-2026-93827 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93827?
No fix for CVE-2026-93827 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93827 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93827

Explore →

Is Your Infrastructure Affected by CVE-2026-93827?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs