CVE-2026-23428

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-03. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-18661 (ENISA EUVD) · GHSA-v45r-hfjf-mq4q (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.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 of share_conf in compound request

smb2_get_ksmbd_tcon() reuses work->tcon in compound requests without validating tcon->t_state. ksmbd_tree_conn_lookup() checks t_state == TREE_CONNECTED on the initial lookup path, but the compound reuse path bypasses this check entirely.

If a prior command in the compound (SMB2_TREE_DISCONNECT) sets t_state to TREE_DISCONNECTED and frees share_conf via ksmbd_share_config_put(), subsequent commands dereference the freed share_conf through work->tcon->share_conf.

KASAN report:

[ 4.144653] ================================================================== [ 4.145059] BUG: KASAN: slab-use-after-free in smb2_write+0xc74/0xe70 [ 4.145415] Read of size 4 at addr ffff88810430c194 by task kworker/1:1/44 [ 4.145772] [ 4.145867] CPU: 1 UID: 0 PID: 44 Comm: kworker/1:1 Not tainted 7.0.0-rc3+ #60 PREEMPTLAZY [ 4.145871] 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 [ 4.145875] Workqueue: ksmbd-io handle_ksmbd_work [ 4.145888] Call Trace: [ 4.145892] [ 4.145894] dump_stack_lvl+0x64/0x80 [ 4.145910] print_report+0xce/0x660 [ 4.145919] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 4.145928] ? smb2_write+0xc74/0xe70 [ 4.145931] kasan_report+0xce/0x100 [ 4.145934] ? smb2_write+0xc74/0xe70 [ 4.145937] smb2_write+0xc74/0xe70 [ 4.145939] ? __pfx_smb2_write+0x10/0x10 [ 4.145942] ? _raw_spin_unlock+0xe/0x30 [ 4.145945] ? ksmbd_smb2_check_message+0xeb2/0x24c0 [ 4.145948] ? smb2_tree_disconnect+0x31c/0x480 [ 4.145951] handle_ksmbd_work+0x40f/0x1080 [ 4.145953] process_one_work+0x5fa/0xef0 [ 4.145962] ? assign_work+0x122/0x3e0 [ 4.145964] worker_thread+0x54b/0xf70 [ 4.145967] ? __pfx_worker_thread+0x10/0x10 [ 4.145970] kthread+0x346/0x470 [ 4.145976] ? recalc_sigpending+0x19b/0x230 [ 4.145980] ? __pfx_kthread+0x10/0x10 [ 4.145984] ret_from_fork+0x4fb/0x6c0 [ 4.145992] ? __pfx_ret_from_fork+0x10/0x10 [ 4.145995] ? __switch_to+0x36c/0xbe0 [ 4.145999] ? __pfx_kthread+0x10/0x10 [ 4.146003] ret_from_fork_asm+0x1a/0x30 [ 4.146013] [ 4.146014] [ 4.149858] Allocated by task 44: [ 4.149953] kasan_save_stack+0x33/0x60 [ 4.150061] kasan_save_track+0x14/0x30 [ 4.150169] __kasan_kmalloc+0x8f/0xa0 [ 4.150274] ksmbd_share_config_get+0x1dd/0xdd0 [ 4.150401] ksmbd_tree_conn_connect+0x7e/0x600 [ 4.150529] smb2_tree_connect+0x2e6/0x1000 [ 4.150645] handle_ksmbd_work+0x40f/0x1080 [ 4.150761] process_one_work+0x5fa/0xef0 [ 4.150873] worker_thread+0x54b/0xf70 [ 4.150978] kthread+0x346/0x470 [ 4.151071] ret_from_fork+0x4fb/0x6c0 [ 4.151176] ret_from_fork_asm+0x1a/0x30 [ 4.151286] [ 4.151332] Freed by task 44: [ 4.151418] kasan_save_stack+0x33/0x60 [ 4.151526] kasan_save_track+0x14/0x30 [ 4.151634] kasan_save_free_info+0x3b/0x60 [ 4.151751] __kasan_slab_free+0x43/0x70 [ 4.151861] kfree+0x1ca/0x430 [ 4.151952] __ksmbd_tree_conn_disconnect+0xc8/0x190 [ 4.152088] smb2_tree_disconnect+0x1cd/0x480 [ 4.152211] handle_ksmbd_work+0x40f/0x1080 [ 4.152326] process_one_work+0x5fa/0xef0 [ 4.152438] worker_thread+0x54b/0xf70 [ 4.152545] kthread+0x346/0x470 [ 4.152638] ret_from_fork+0x4fb/0x6c0 [ 4.152743] ret_from_fork_asm+0x1a/0x30 [ 4.152853] [ 4.152900] The buggy address belongs to the object at ffff88810430c180 [ 4.152900] which belongs to the cache kmalloc-96 of size 96 [ 4.153226] The buggy address is located 20 bytes inside of [ 4.153226] freed 96-byte region [ffff88810430c180, ffff88810430c1e0) [ 4.153549] [ 4.153596] The buggy address belongs to the physical page: [ 4.153750] page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff88810430ce80 pfn:0x10430c [ 4.154000] flags: 0x ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
26th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

October 19, 2026

Advisory Details (7)

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

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c33615f995aee80657b9fdfbc4ee7f49c2bd733d
Web page

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a5929c2020ce54e1dcbd1078c0f30b8aaf73c105
Web page

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f7468fd2a7554cea91b7d430335a3dbf01dcc09
Web page

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c742b46a153d3ff95ff0825ab1950c87b9e14470
Web page

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/806f13752652216db0c309392b4db3e64eeed4f2
Web page

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eae0dc86f71e6f3294c0cd7ffc05039258d243af
Web page

ksmbd: fix use-after-free of share_conf in compound request - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-23428(1)

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

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-40.40) @ questing2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.185.166) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04 (6.17.0-1026.26) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1108.114~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.17.0-1017.19~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-10-27ubuntu
ubuntulowlatency-4.4 (4.4.0-243) @ xenial2026-10-27ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1116.101) @ jammy2026-10-27ubuntu
ubuntulowlatency (5.15.0-25) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1028.28) @ noble2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1106.112~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1105.103) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-6.17 (6.17.0-1021.21) @ questing2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1074 (5.15.0-1074.78) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.17 (6.17.0-1018.18~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1021.21~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-40.40~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
linuxKernel @ 5.15.203 (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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
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

(25)

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 11× in last 7d / 56× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 99 of 334 refreshes 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 235 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-23428?
CVE-2026-23428 is a high-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 of share_conf in compound request smb2getksmbd_tcon() reuses work->tcon in compound requests without validating tcon->tstate. ksmbdtreeconnlookup() checks t_state == TREE_CONNECTED on the initial lookup…
When was the CVE record for CVE-2026-23428 published?
The CVE record for CVE-2026-23428 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-23428 actively exploited?
CVE-2026-23428 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23428?
CVE-2026-23428 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23428?
A fix for CVE-2026-23428 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23428 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-23428

Explore →

Is Your Infrastructure Affected by CVE-2026-23428?

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