CVE-2026-93196

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. 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.2%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:

nvdimm: virtio_pmem: refcount requests for token lifetime

KASAN reports slab-use-after-free in __wake_up_common(): BUG: KASAN: slab-use-after-free in __wake_up_common+0x114/0x160 Read of size 8 at addr ffff88810fdcb710 by task swapper/0/0

CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.19.0-next-20260220-00006-g1eae5f204ec3 #4 PREEMPT(full) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 Call Trace: dump_stack_lvl+0x6d/0xb0 print_report+0x170/0x4e2 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 ? __virt_addr_valid+0x1dc/0x380 kasan_report+0xbc/0xf0 ? __wake_up_common+0x114/0x160 ? __wake_up_common+0x114/0x160 __wake_up_common+0x114/0x160 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 __wake_up+0x36/0x60 virtio_pmem_host_ack+0x11d/0x3b0 ? sched_balance_domains+0x29f/0xb00 ? __pfx_virtio_pmem_host_ack+0x10/0x10 ? _raw_spin_lock_irqsave+0x98/0x100 ? __pfx__raw_spin_lock_irqsave+0x10/0x10 vring_interrupt+0x1c9/0x5e0 ? __pfx_vp_interrupt+0x10/0x10 vp_vring_interrupt+0x87/0x100 ? __pfx_vp_interrupt+0x10/0x10 __handle_irq_event_percpu+0x17f/0x550 ? __pfx__raw_spin_lock+0x10/0x10 handle_irq_event+0xab/0x1c0 handle_fasteoi_irq+0x276/0xae0 __common_interrupt+0x65/0x130 common_interrupt+0x78/0xa0

virtio_pmem_host_ack() wakes a request that has already been freed by the submitter.

This happens when the request token is still reachable via the virtqueue, but virtio_pmem_flush() returns and frees it.

Fix the token lifetime by refcounting struct virtio_pmem_request. virtio_pmem_flush() holds a submitter reference, and the virtqueue holds an extra reference once the request is queued. The completion path drops the virtqueue reference, and the submitter drops its reference before returning.

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.2%
EPSS %ILE
7th
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 17, 2026

Last Modified

October 3, 2026

Advisory Details (3)

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

nvdimm: virtio_pmem: refcount requests for token lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e57140944b5a47a7fd5a142faab29a02af040bc8
generic

nvdimm: virtio_pmem: refcount requests for token lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1e740b9156621afd4c4aa66257f4dde8df1febe
generic

nvdimm: virtio_pmem: refcount requests for token lifetime - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be072a5d5e35f4bdf2da22f600b5d6dc6c5ff491

Vendor Advisories for CVE-2026-93196(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
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
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 28× in last 7d / 74× 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 08:23 UTCEG score recompute
  2. 2026-10-05 08:23 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 21:11 UTCGHSA enrichment
  5. 2026-10-04 09:57 UTCGHSA enrichment
  6. 2026-10-03 22:45 UTCEG score recompute
  7. 2026-10-03 22:45 UTCGHSA enrichment
  8. 2026-10-03 11:33 UTCGHSA enrichment
  9. 2026-10-03 07:23 UTCGHSA enrichment
  10. 2026-10-02 20:12 UTCEG score recompute
  11. 2026-10-02 20:11 UTCGHSA enrichment
  12. 2026-10-02 08:58 UTCGHSA enrichment
  13. 2026-10-01 21:41 UTCEG score recompute
  14. 2026-10-01 21:40 UTCGHSA enrichment
  15. 2026-10-01 19:51 UTCEPSS rescore
  16. 2026-10-01 10:26 UTCGHSA enrichment
  17. 2026-09-30 23:14 UTCEG score recompute
  18. 2026-09-30 23:14 UTCGHSA enrichment
  19. 2026-09-30 15:04 UTCEPSS rescore
  20. 2026-09-30 11:54 UTCGHSA enrichment
  21. 2026-09-30 00:43 UTCEG score recompute
  22. 2026-09-30 00:43 UTCGHSA enrichment
  23. 2026-09-29 12:04 UTCGHSA enrichment
  24. 2026-09-29 00:49 UTCEG score recompute
  25. 2026-09-29 00:49 UTCGHSA enrichment
Show 49 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 13:36 UTCGHSA enrichment
  4. 2026-09-28 02:25 UTCGHSA enrichment
  5. 2026-09-27 15:14 UTCEG score recompute
  6. 2026-09-27 15:14 UTCGHSA enrichment
  7. 2026-09-27 13:49 UTCEPSS rescore
  8. 2026-09-27 04:01 UTCGHSA enrichment
  9. 2026-09-26 16:49 UTCEG score recompute
  10. 2026-09-26 16:49 UTCGHSA enrichment
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 05:38 UTCEG score recompute
  13. 2026-09-26 05:37 UTCGHSA enrichment
  14. 2026-09-25 18:25 UTCGHSA enrichment
  15. 2026-09-25 07:14 UTCGHSA enrichment
  16. 2026-09-24 20:02 UTCEG score recompute
  17. 2026-09-24 20:02 UTCGHSA enrichment
  18. 2026-09-24 14:04 UTCEPSS rescore
  19. 2026-09-24 08:50 UTCGHSA enrichment
  20. 2026-09-23 21:39 UTCEG score recompute
  21. 2026-09-23 21:39 UTCGHSA enrichment
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-23 10:28 UTCGHSA enrichment
  24. 2026-09-22 23:16 UTCEG score recompute
  25. 2026-09-22 23:15 UTCGHSA enrichment
  26. 2026-09-22 16:01 UTCEPSS rescore
  27. 2026-09-22 12:00 UTCGHSA enrichment
  28. 2026-09-22 00:48 UTCEG score recompute
  29. 2026-09-22 00:48 UTCGHSA enrichment
  30. 2026-09-21 21:09 UTCEPSS rescore
  31. 2026-09-21 13:37 UTCGHSA enrichment
  32. 2026-09-21 02:26 UTCEG score recompute
  33. 2026-09-21 02:26 UTCGHSA enrichment
  34. 2026-09-20 20:16 UTCEPSS rescore
  35. 2026-09-20 15:14 UTCGHSA enrichment
  36. 2026-09-20 04:01 UTCGHSA enrichment
  37. 2026-09-19 16:49 UTCEG score recompute
  38. 2026-09-19 16:49 UTCGHSA enrichment
  39. 2026-09-19 05:37 UTCEG score recompute
  40. 2026-09-19 05:37 UTCGHSA enrichment
  41. 2026-09-18 19:28 UTCEPSS rescore
  42. 2026-09-18 18:26 UTCEG score recompute
  43. 2026-09-18 18:26 UTCGHSA enrichment
  44. 2026-09-18 18:00 UTCEG score recompute▲ 8.40
  45. 2026-09-18 18:00 UTCGHSA enrichment
  46. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 8.4 · severity → HIGH
  47. 2026-09-17 17:24 UTCNVD update
  48. 2026-09-17 16:20 UTCEG score recompute
  49. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93196?
CVE-2026-93196 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: nvdimm: virtio_pmem: refcount requests for token lifetime KASAN reports slab-use-after-free in wakeupcommon(): BUG: KASAN: slab-use-after-free in wakeupcommon+0x114/0x160 Read of size 8 at addr ffff88810fdcb710 by task swapper/0/0…
When was CVE-2026-93196 disclosed?
CVE-2026-93196 was first published on September 17, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93196 actively exploited?
CVE-2026-93196 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93196?
CVE-2026-93196 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-93196?
No fix for CVE-2026-93196 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-93196 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-93196

Explore →

Is Your Infrastructure Affected by CVE-2026-93196?

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

Book a Demo →Browse All CVEs