CVE-2026-23428

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 74% 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 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
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
26%
KEV
Not listed

Published

April 3, 2026

Last Modified

August 5, 2026

Advisory Details (7)

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

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.203—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 rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
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

(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 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 267 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:35 UTCVendor advisory
  8. 2026-08-14 22:35 UTCGHSA enrichment
  9. 2026-08-14 18:52 UTCVendor advisory
  10. 2026-08-14 18:52 UTCGHSA enrichment
  11. 2026-08-14 13:10 UTCVendor advisory
  12. 2026-08-14 13:10 UTCGHSA enrichment
  13. 2026-08-14 09:27 UTCVendor advisory
  14. 2026-08-14 09:27 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 03:24 UTCVendor advisory
  22. 2026-08-13 03:24 UTCGHSA enrichment
  23. 2026-08-12 23:42 UTCVendor advisory
  24. 2026-08-12 23:42 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:09 UTCVendor advisory
  36. 2026-08-11 07:09 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 11:58 UTCVendor advisory
  42. 2026-08-10 11:57 UTCGHSA enrichment
  43. 2026-08-10 07:37 UTCVendor advisory
  44. 2026-08-10 07:37 UTCGHSA enrichment
  45. 2026-08-10 03:53 UTCVendor advisory
  46. 2026-08-10 03:53 UTCGHSA enrichment
  47. 2026-08-10 00:10 UTCVendor advisory
  48. 2026-08-10 00:10 UTCGHSA enrichment
  49. 2026-08-09 20:26 UTCVendor advisory
  50. 2026-08-09 20:26 UTCGHSA enrichment
  51. 2026-08-09 16:44 UTCEG score recompute
  52. 2026-08-09 16:44 UTCVendor advisory
  53. 2026-08-09 16:44 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 08:58 UTCVendor advisory
  58. 2026-08-09 08:58 UTCGHSA enrichment
  59. 2026-08-09 05:15 UTCEG score recompute
  60. 2026-08-09 05:15 UTCVendor advisory
  61. 2026-08-09 05:15 UTCGHSA enrichment
  62. 2026-08-08 16:37 UTCEPSS rescore
  63. 2026-08-08 09:56 UTCVendor advisory
  64. 2026-08-08 09:56 UTCGHSA enrichment
  65. 2026-08-08 06:13 UTCVendor advisory
  66. 2026-08-08 06:13 UTCGHSA enrichment
  67. 2026-08-08 02:30 UTCVendor advisory
  68. 2026-08-08 02:30 UTCGHSA enrichment
  69. 2026-08-07 22:47 UTCVendor advisory
  70. 2026-08-07 22:47 UTCGHSA enrichment
  71. 2026-08-07 19:04 UTCEG score recompute
  72. 2026-08-07 19:04 UTCVendor advisory
  73. 2026-08-07 19:04 UTCGHSA enrichment
  74. 2026-08-07 15:22 UTCVendor advisory
  75. 2026-08-07 15:22 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-23428?
CVE-2026-23428 is a critical vulnerability 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 CVE-2026-23428 disclosed?
CVE-2026-23428 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-23428 actively exploited?
CVE-2026-23428 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 73.9% of all scored CVEs.
What is the CVSS score of CVE-2026-23428?
CVE-2026-23428 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-23428?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23428, 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-23428

Explore →

Is Your Infrastructure Affected by CVE-2026-23428?

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

Start Free Scan →Browse All CVEs