CVE-2026-23364

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-03-25. the CNA's CVSS baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: 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: Compare MACs in constant time

To prevent timing attacks, MAC comparisons need to be constant-time. Replace the memcmp() with the correct function, crypto_memneq().

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity74% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

March 25, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jun 19, 2026
No patch confirmed yet.
generic

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93c0a22fec914ec4b697e464895a0f594e29fb28
generic

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a665d733940592e671ec6afadcd0be80a091a80
generic

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/307afccb751f542246bd5dc68a2c1ffe1a78418c
generic

ksmbd: Compare MACs in constant time - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2cdc56ed67615ba0921383a688f24415ebe065f3

Vendor Advisories for CVE-2026-23364(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.15.210—osv
linuxKernel @ 6.1.167—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 (117 versions)6.19.8-1—

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 60× 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 217 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23364?
CVE-2026-23364 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: Compare MACs in constant time To prevent timing attacks, MAC comparisons need to be constant-time. Replace the memcmp() with the correct function, crypto_memneq().
When was CVE-2026-23364 disclosed?
CVE-2026-23364 was first published in the National Vulnerability Database on March 25, 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-23364 actively exploited?
CVE-2026-23364 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 67.7% of all scored CVEs.
What is the CVSS score of CVE-2026-23364?
CVE-2026-23364 has a CVSS v4.0 base score of 7.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-23364?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23364, 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-23364

Explore →

Is Your Infrastructure Affected by CVE-2026-23364?

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

Start Free Scan →Browse All CVEs