CVE-2026-23427

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-03) is not newer than that change (2026-08-05), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-18659 (ENISA EUVD) · GHSA-vrjp-x986-3fqm (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Oct 31, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-11-12ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-11-12ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-11-12ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1017.19) @ questing2026-11-12ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-11-12ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-11-12ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-11-12ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-11-12ubuntu
linuxKernel @ 6.6.130 (fixes >=0)—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 rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (123 versions)
  • every version up to 6.19.10-1: fixed in 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 15× in last 7d / 74× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 402 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 302 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-11-13 16:05 UTCEchelonGraph re-scored
  3. 2026-11-13 16:05 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-11-12 16:15 UTCEchelonGraph re-scored
  6. 2026-11-12 16:15 UTCVendor advisory
  7. 2026-11-12 16:15 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-11-11 16:22 UTCEchelonGraph re-scored
  10. 2026-11-11 16:22 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  12. 2026-11-10 16:34 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-11-09 16:44 UTCEchelonGraph re-scored
  14. 2026-11-09 16:44 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-11-08 16:58 UTCEchelonGraph re-scored
  17. 2026-11-08 16:58 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-11-07 17:12 UTCEchelonGraph re-scored
  20. 2026-11-07 17:12 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  22. 2026-11-06 17:26 UTCEchelonGraph re-scored
  23. 2026-11-06 17:26 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-11-06 03:25 UTCOSV refresh
Show 75 more
  1. 2026-11-05 17:40 UTCEchelonGraph re-scored
  2. 2026-11-05 17:40 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-11-04 17:54 UTCEchelonGraph re-scored
  5. 2026-11-04 17:54 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-11-03 18:08 UTCEchelonGraph re-scored
  8. 2026-11-03 18:08 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  10. 2026-11-02 18:19 UTCEchelonGraph re-scored
  11. 2026-11-02 18:19 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-11-01 18:33 UTCEchelonGraph re-scored
  14. 2026-11-01 18:33 UTCVendor advisory
  15. 2026-11-01 18:32 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  17. 2026-10-31 18:46 UTCEchelonGraph re-scored
  18. 2026-10-31 18:46 UTCVendor advisory
  19. 2026-10-31 18:46 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-30 19:00 UTCEchelonGraph re-scored
  22. 2026-10-30 19:00 UTCVendor advisory
  23. 2026-10-30 19:00 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-29 19:14 UTCEchelonGraph re-scored
  26. 2026-10-29 19:14 UTCVendor advisory
  27. 2026-10-29 19:14 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-10-28 19:29 UTCEchelonGraph re-scored
  30. 2026-10-28 19:29 UTCVendor advisory
  31. 2026-10-28 19:28 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-10-27 19:41 UTCEchelonGraph re-scored
  34. 2026-10-27 19:41 UTCVendor advisory
  35. 2026-10-27 19:41 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  37. 2026-10-26 19:55 UTCEchelonGraph re-scored
  38. 2026-10-26 19:55 UTCVendor advisory
  39. 2026-10-26 19:55 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  41. 2026-10-25 17:57 UTCEchelonGraph re-scored
  42. 2026-10-25 17:57 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  44. 2026-10-25 14:41 UTCEchelonGraph re-scored
  45. 2026-10-24 17:37 UTCEchelonGraph re-scored
  46. 2026-10-24 17:37 UTCVendor advisory
  47. 2026-10-24 17:37 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  49. 2026-10-23 17:52 UTCEchelonGraph re-scored
  50. 2026-10-23 17:52 UTCVendor advisory
  51. 2026-10-23 17:52 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  53. 2026-10-22 18:05 UTCEchelonGraph re-scored
  54. 2026-10-22 18:05 UTCVendor advisory
  55. 2026-10-22 18:05 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  57. 2026-10-21 18:19 UTCEchelonGraph re-scored
  58. 2026-10-21 18:19 UTCVendor advisory
  59. 2026-10-21 18:19 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  61. 2026-10-20 18:33 UTCEchelonGraph re-scored
  62. 2026-10-20 18:33 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-10-19 18:40 UTCEchelonGraph re-scored
  65. 2026-10-19 18:40 UTCVendor advisory
  66. 2026-10-19 18:39 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  68. 2026-10-18 18:47 UTCEchelonGraph re-scored
  69. 2026-10-18 18:47 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  71. 2026-10-18 03:54 UTCEchelonGraph re-scored
  72. 2026-10-17 19:00 UTCEchelonGraph re-scored
  73. 2026-10-17 19:00 UTCGHSA enrichmentGHSA-vrjp-x986-3fqm · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  75. 2026-10-16 19:13 UTCEchelonGraph re-scored

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23427?
CVE-2026-23427 is a critical-severity vulnerability; its CVE record was 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 parse_durable_handle_context() unconditionally assigns dh_info->fp->conn to the current connection when handling a DURABLE_REQ_V2 context with…
When was the CVE record for CVE-2026-23427 published?
The CVE record for CVE-2026-23427 was published on April 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-23427 actively exploited?
CVE-2026-23427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-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?
A fix for CVE-2026-23427 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs