CVE-2026-31612

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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: validate EaNameLength in smb2_get_ea()

smb2_get_ea() reads ea_req->EaNameLength from the client request and passes it directly to strncmp() as the comparison length without verifying that the length of the name really is the size of the input buffer received.

Fix this up by properly checking the size of the name based on the value received and the overall size of the request, to prevent a later strncmp() call to use the length as a "trusted" size of the buffer. Without this check, uninitialized heap values might be slowly leaked to the client.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
33.7%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66751841212c2cc196577453c37f7774ff363f02
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/551dfb15b182abad4600eaf7b37e6eb7000d5b1b
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b73376feecb3b61172fe5b4ff42bbbb8531669d
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3363a770b193f555f29d76ddf4ced3305c0ccf6d
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/243b206bcb5a7137e8bddd57b2eec81e1ebd3859

Vendor Advisories for CVE-2026-31612(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-31612?
CVE-2026-31612 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate EaNameLength in smb2getea() smb2getea() reads ea_req->EaNameLength from the client request and passes it directly to strncmp() as the comparison length without verifying that the length of the name really is the…
When was CVE-2026-31612 disclosed?
CVE-2026-31612 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31612 actively exploited?
CVE-2026-31612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31612?
CVE-2026-31612 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31612?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31612, 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

Explore the affected products and dependency analysis for CVE-2026-31612

Explore →

Is Your Infrastructure Affected by CVE-2026-31612?

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

Start Free Scan →Browse All CVEs