CVE-2026-23427

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix use-after-free in durable v2 replay of active file handles

parse_durable_handle_context() unconditionally assigns dh_info->fp->conn to the current connection when handling a DURABLE_REQ_V2 context with SMB2_FLAGS_REPLAY_OPERATION. ksmbd_lookup_fd_cguid() does not filter by fp->conn, so it returns file handles that are already actively connected. The unconditional overwrite replaces fp->conn, and when the overwriting connection is subsequently freed, __ksmbd_close_fd() dereferences the stale fp->conn via spin_lock(&fp->conn->llist_lock), causing a use-after-free.

KASAN report:

[ 7.349357] ================================================================== [ 7.349607] BUG: KASAN: slab-use-after-free in _raw_spin_lock+0x75/0xe0 [ 7.349811] Write of size 4 at addr ffff8881056ac18c by task kworker/1:2/108 [ 7.350010] [ 7.350064] CPU: 1 UID: 0 PID: 108 Comm: kworker/1:2 Not tainted 7.0.0-rc3+ #58 PREEMPTLAZY [ 7.350068] Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 7.350070] Workqueue: ksmbd-io handle_ksmbd_work [ 7.350083] Call Trace: [ 7.350087] [ 7.350087] dump_stack_lvl+0x64/0x80 [ 7.350094] print_report+0xce/0x660 [ 7.350100] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 7.350101] ? __pfx___mod_timer+0x10/0x10 [ 7.350106] ? _raw_spin_lock+0x75/0xe0 [ 7.350108] kasan_report+0xce/0x100 [ 7.350109] ? _raw_spin_lock+0x75/0xe0 [ 7.350114] kasan_check_range+0x105/0x1b0 [ 7.350116] _raw_spin_lock+0x75/0xe0 [ 7.350118] ? __pfx__raw_spin_lock+0x10/0x10 [ 7.350119] ? __call_rcu_common.constprop.0+0x25e/0x780 [ 7.350125] ? close_id_del_oplock+0x2cc/0x4e0 [ 7.350128] __ksmbd_close_fd+0x27f/0xaf0 [ 7.350131] ksmbd_close_fd+0x135/0x1b0 [ 7.350133] smb2_close+0xb19/0x15b0 [ 7.350142] ? __pfx_smb2_close+0x10/0x10 [ 7.350143] ? xas_load+0x18/0x270 [ 7.350146] ? _raw_spin_lock+0x84/0xe0 [ 7.350148] ? __pfx__raw_spin_lock+0x10/0x10 [ 7.350150] ? _raw_spin_unlock+0xe/0x30 [ 7.350151] ? ksmbd_smb2_check_message+0xeb2/0x24c0 [ 7.350153] ? ksmbd_tree_conn_lookup+0xcd/0xf0 [ 7.350154] handle_ksmbd_work+0x40f/0x1080 [ 7.350156] process_one_work+0x5fa/0xef0 [ 7.350162] ? assign_work+0x122/0x3e0 [ 7.350163] worker_thread+0x54b/0xf70 [ 7.350165] ? __pfx_worker_thread+0x10/0x10 [ 7.350166] kthread+0x346/0x470 [ 7.350170] ? recalc_sigpending+0x19b/0x230 [ 7.350176] ? __pfx_kthread+0x10/0x10 [ 7.350178] ret_from_fork+0x4fb/0x6c0 [ 7.350183] ? __pfx_ret_from_fork+0x10/0x10 [ 7.350185] ? __switch_to+0x36c/0xbe0 [ 7.350188] ? __pfx_kthread+0x10/0x10 [ 7.350190] ret_from_fork_asm+0x1a/0x30 [ 7.350197] [ 7.350197] [ 7.355160] Allocated by task 123: [ 7.355261] kasan_save_stack+0x33/0x60 [ 7.355373] kasan_save_track+0x14/0x30 [ 7.355484] __kasan_kmalloc+0x8f/0xa0 [ 7.355593] ksmbd_conn_alloc+0x44/0x6d0 [ 7.355711] ksmbd_kthread_fn+0x243/0xd70 [ 7.355839] kthread+0x346/0x470 [ 7.355942] ret_from_fork+0x4fb/0x6c0 [ 7.356051] ret_from_fork_asm+0x1a/0x30 [ 7.356164] [ 7.356214] Freed by task 134: [ 7.356305] kasan_save_stack+0x33/0x60 [ 7.356416] kasan_save_track+0x14/0x30 [ 7.356527] kasan_save_free_info+0x3b/0x60 [ 7.356646] __kasan_slab_free+0x43/0x70 [ 7.356761] kfree+0x1ca/0x430 [ 7.356862] ksmbd_tcp_disconnect+0x59/0xe0 [ 7.356993] ksmbd_conn_handler_loop+0x77e/0xd40 [ 7.357138] kthread+0x346/0x470 [ 7.357240] ret_from_fork+0x4fb/0x6c0 [ 7.357350] ret_from_fork_asm+0x1a/0x30 [ 7.357463] [ 7.357513] The buggy address belongs to the object at ffff8881056ac000 [ 7.357513] which belongs to the cache kmalloc-1k of size 1024 [ 7.357857] The buggy address is located 396 bytes inside of [ 7.357857] freed 1024-byte region ---truncated---

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (5)

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

ksmbd: fix use-after-free in durable v2 replay of active file handles - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix use-after-free in durable v2 replay of active file handles - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b0792c3eacf01e67f356d6ef9707b0ae5022419
generic

ksmbd: fix use-after-free in durable v2 replay of active file handles - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix use-after-free in durable v2 replay of active file handles - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/568a25fd7bcdfb2790f7d42aa2a440dca4435c96
generic

ksmbd: fix use-after-free in durable v2 replay of active file handles - kernel/git/stable/linux.git - Linux kernel stable tree

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.6.130—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 29× 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.

Showing the most recent 100 of 261 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-02 11:14 UTCOSV refresh
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 09:18 UTCEG score recompute
  3. 2026-08-16 09:18 UTCVendor advisory
  4. 2026-08-16 09:18 UTCGHSA enrichment
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 22:54 UTCVendor advisory
  8. 2026-08-14 22:54 UTCGHSA enrichment
  9. 2026-08-14 18:52 UTCVendor advisory
  10. 2026-08-14 18:52 UTCGHSA enrichment
  11. 2026-08-14 13:49 UTCVendor advisory
  12. 2026-08-14 13:49 UTCGHSA enrichment
  13. 2026-08-14 09:47 UTCVendor advisory
  14. 2026-08-14 09:47 UTCGHSA enrichment
  15. 2026-08-14 05:44 UTCEG score recompute
  16. 2026-08-14 05:44 UTCVendor advisory
  17. 2026-08-14 05:44 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 09:56 UTCVendor advisory
  20. 2026-08-13 09:56 UTCGHSA enrichment
  21. 2026-08-13 04:04 UTCVendor advisory
  22. 2026-08-13 04:04 UTCGHSA enrichment
  23. 2026-08-13 00:01 UTCVendor advisory
  24. 2026-08-13 00:01 UTCGHSA enrichment
  25. 2026-08-12 19:59 UTCEG score recompute
  26. 2026-08-12 19:59 UTCVendor advisory
  27. 2026-08-12 19:59 UTCGHSA enrichment
  28. 2026-08-12 13:50 UTCEPSS rescore
  29. 2026-08-12 00:40 UTCVendor advisory
  30. 2026-08-12 00:39 UTCGHSA enrichment
  31. 2026-08-11 20:26 UTCEG score recompute
  32. 2026-08-11 20:26 UTCVendor advisory
  33. 2026-08-11 20:26 UTCGHSA enrichment
  34. 2026-08-11 13:42 UTCEPSS rescore
  35. 2026-08-11 07:29 UTCVendor advisory
  36. 2026-08-11 07:29 UTCGHSA enrichment
  37. 2026-08-11 03:27 UTCEG score recompute
  38. 2026-08-11 03:27 UTCVendor advisory
  39. 2026-08-11 03:27 UTCGHSA enrichment
  40. 2026-08-11 00:00 UTCEPSS rescore
  41. 2026-08-10 13:17 UTCVendor advisory
  42. 2026-08-10 13:17 UTCGHSA enrichment
  43. 2026-08-10 09:14 UTCVendor advisory
  44. 2026-08-10 09:14 UTCGHSA enrichment
  45. 2026-08-10 05:11 UTCVendor advisory
  46. 2026-08-10 05:11 UTCGHSA enrichment
  47. 2026-08-10 01:09 UTCVendor advisory
  48. 2026-08-10 01:09 UTCGHSA enrichment
  49. 2026-08-09 21:04 UTCVendor advisory
  50. 2026-08-09 21:04 UTCGHSA enrichment
  51. 2026-08-09 17:01 UTCEG score recompute
  52. 2026-08-09 17:01 UTCVendor advisory
  53. 2026-08-09 17:01 UTCGHSA enrichment
  54. 2026-08-09 13:46 UTCEPSS rescore
  55. 2026-08-09 12:59 UTCVendor advisory
  56. 2026-08-09 12:59 UTCGHSA enrichment
  57. 2026-08-09 05:15 UTCEG score recompute
  58. 2026-08-09 05:15 UTCVendor advisory
  59. 2026-08-09 05:15 UTCGHSA enrichment
  60. 2026-08-08 16:37 UTCEPSS rescore
  61. 2026-08-08 11:35 UTCVendor advisory
  62. 2026-08-08 11:34 UTCGHSA enrichment
  63. 2026-08-08 07:31 UTCVendor advisory
  64. 2026-08-08 07:31 UTCGHSA enrichment
  65. 2026-08-08 03:29 UTCVendor advisory
  66. 2026-08-08 03:29 UTCGHSA enrichment
  67. 2026-08-07 23:26 UTCVendor advisory
  68. 2026-08-07 23:26 UTCGHSA enrichment
  69. 2026-08-07 19:24 UTCEG score recompute
  70. 2026-08-07 19:24 UTCVendor advisory
  71. 2026-08-07 19:24 UTCGHSA enrichment
  72. 2026-08-07 15:22 UTCVendor advisory
  73. 2026-08-07 15:22 UTCGHSA enrichment
  74. 2026-08-06 17:42 UTCEG score recompute
  75. 2026-08-06 17:42 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-23427?
CVE-2026-23427 is a critical vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in durable v2 replay of active file handles parsedurablehandlecontext() unconditionally assigns dhinfo->fp->conn to the current connection when handling a DURABLEREQV2 context with…
When was CVE-2026-23427 disclosed?
CVE-2026-23427 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23427 actively exploited?
CVE-2026-23427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.5% of all scored CVEs.
What is the CVSS score of CVE-2026-23427?
CVE-2026-23427 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-23427?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23427, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-23427?

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

Start Free Scan →Browse All CVEs